Histórico da Página

• • The tags not used by PCP Protheus x PC-Factory integration, even in messages, described in Schema of TOTVS Single Message are not mentioned in this document.
  • The tag Type (Order Type) is generated with value "1" - Internal Order.
  • The tag RequestType (Request Type) identifies if the request can be done separately from the production report, according to rule below:
    If parameter MV_REQAUT has 'D' the DIRECT materials are entered and the INDIRECT are automatically loaded;
    If parameter MV_REQAUT has 'A' the consumption of materials is executed in all components;
    This tag has the following values: 1-Direct, 2-Indirect.
  • The tag Allocation Type (Allocation Type) is generated with value "3" - Absolute Order.
  • The session ListOfAllocatedMaterial follows some rules for allocation: 
    If item controls address and did not generate SBC it does not generate data from list  ListOfAllocatedMaterial (verificar only when parameter MV_LOCALIZ = S);
    If item controls trace and did not generate the batch in SD4,  it does not generate data from list ListOfAllocatedMaterial;
    If item does not control address or batch, it must generate data from list  ListOfAllocatedMaterial based on SD4.
  • The tags of operations os session order ListOfActivityOrders can have different origin according to parameterization or executed routines. If you execute the machine MATA690, table SH8 is used. When parameter MV_PCPATOR has 'S', table SHY is used. If parameter MV_PCPATOR has 'N', table SG2 is used. 
  • The tag Split of session ListOfActivityOrders is generated when there is unfolding of operation in several resources. Generated when using Shop Floor.
  • The tag ActivityType (Operation Type) is generated with value '1' - Register;
  • The tag UnitTimeType (Unit Measure Type) is generated with value '1' - Time;
  • The tag UnitItemNumber is used to register the standard batch of operation production.
  • For PC-Factory, indicate in which operation the component is consumed. When component x operation concept is not used, link components in last operation.
  • The tag TimeMachine (Machine Time) indicates time for production order.
    By using parameter MV_PCPATOR the time is SHY.HY_TEMPOM.
    When machine load is used, use the difference between SH8.H8_HRINI and SH8.H8_HRFIM.
    The time can have variation according to Operation Type (when it is not in SHY):
    Operation Type 1 Regular: Apply the batch time the quantity of order. Which are: (SG2.G2_TEMPAD / SG2.G2_LOTEPAD) * SC2.C2_QUANT) / SH1.H1_MAOOBRA. Note: If time and lot are zero, consider 1.
    Operation Type 2 Fixed and 3 Unlimited: Regardless of amount, the time is the same. Which are: SG2.G2_TEMPAD. Note: If zero delivers 1.
    Operation Type 4 Minimum Time: Considers the multiple quantity of batch. Example: Lot = 10. Time = 5. Order Amt. = 7. It must consider time to make 10 spare parts. The same calculation is type 1 Regular.
    Another point to consider is the PC-Factory waits time in Centesimal. When parameter MV_TPHR is other than 'C', time is converted to centesimal.
  • The tag TimeResource (Resource Time) indicates tiem to make standard batch.
  • The tag LaborCode (Labor Code) is indicated by 'MOD' + Cost Center.
  • The session ListOfQuotaActivity is generated only when Shop Floor is active.
  • The tag StatusActivityType has the following values: 1=Not Started;2=Programmed;3=Released;4=Started;5=Finished;6=Suspended
  • O The co-produto será enviado ao product is sent to PC-Factory na ListOfMaterialOrders, tag MaterialQuantity, e na ListOfAllocatedMaterial, tag AllocationQuantity (quando existir) com quantidade negativa. O PC-Factory deverá enviar ao Protheus na mensagem de apontamento ProductionAppointment na SupplyOrder a the tag UsedQuantity com quantidade negativa, com isso o ERP entenderá que se trata de uma entrada de co-produto no estoque. O tipo de movimento para co-produto, será cadastrado no PCPA109 e deverá ter um conteúdo menor que 500 por se tratar de uma entrada e também deve ser do tipo de DEVOLUÇÃO e o campo Atualiza Empenho deve estar como sim (rotina with negative quantity, then the ERP understands that it is the input of a co-product in stock. The type of transaction for co-product, it is registered in the PCPA109 and must have content lower than 500, as it is an input and must be type RETURN and the field Update Allocation must be yes (routine MATA230).
  •  A tag TimeIndMES deve ser gerada como '3'. 

This message is generated by PC-Factory and sent to Protheus.

• • The default annotation for this integration is MATA681.
  • The fields Machine, Production Order, Operation, Product and Date/Time Report are mandatory.
  • If Report Date/Time is earlier than the current date, the system uses the current Date/Time, that is, date and time the integration is being processed.
  • If the deposit code field is without completion, use the default location of item register(SB1.B1_LOCPAD).
  • The field CloseOperation indicates whether the annotation is TOTAL or PARTIAL. If you send true, it must be T=total. If false, it is considered as P=Partial. 
    The following rule is used to finish the order/production in Protheus is used.
    Close OPERATION: The following TAGS must be entered: ProductionOrderNumber, ActivityCode, CloseOperation (TRUE when TOTAL annotation or closed/finished operation), ReportDateTime. The other quantity fields(ApprovedQuantity and ScrapQuantity) and date/time start/end (StartReportDateTime and EndReportDateTime) must be passed without value (blank)
    Close ORDER: Annotation of quantity in the last operation with tag CloseOperation = TRUE. Encerrar a ORDEM: Realizar o encerramento da ordem sem necessidade de informações de apontamento no XML. Considera somente as tags ProductionOrderNumber e CloseOperation(TRUE). Sendo que, deverá verificar se tem apontamento na última operação. Deverá executar o mesmo procedimento da opção "Encerrar" do MATA681. Devendo fazer as movimentações e atualização do campo SC.C2_DATRF.
  • Every annotation must send a return message, indicating possible problems or processing performed with success. 
    In case of success, the number of annotation is sent to Pc-Factory in the return message of ProductionAnnotation and corresponds to RECNO of SH6. This same number is used when a reverse must be registered(IntegrationReport).
  • The reversal when the field ReversedReport (Annotation Reversal) with content TRUE.
    When is reversal, it must have  the number of annotation, field IntegrationReport. Poderá conter uma lista de Ids(ListOfReversalAppointments) que serão estornados. Pode estornar registros de apontamentos de produção e registros de recusa. Para isso a tag ReversalType indica qual o processo a ser executado, sendo, 1 = Produção; 2 = Recusa
  • The reversal can be generated in two ways in the file: only reversal or reversal + annotation. 
    Only reversal: it has approved quantity and zeroed scrap (or without content) and ReversedReport data.
    Reversal + annotation: with ReversedReport indicated and order data and quantity approved or scrap than zero.
  • The field SH6.H6_OBSERVA = 'TOTVSMES' is automatically registered to indicate the record was generated through TOTVSMES integration.
  • The system PC-Factory uses the format of hours with HH:MM:SS. For PCP Protheus, only HH:MM is considered. Annotation with time lower than 1 minute is rejected.
  • Import respects parameters defined in routines MATA681 through function F12 for user "admin".
  • As in PC-Factory, the operation can be issued later to the annotation, the following rule is used:
    The following TAGS must be entered:
    ProductionOrderNumber: Production Order 
    ActivityCode: Operation 
    CloseOperation: True or False. If TRUE when TOTAL annotation or closed/finalized operation. False in case of PARTIAL operation. 
    ReportDateTime: Annotation date.
  • The other quantity fields(ApprovedQuantity and ScrapQuantity) and date/time start/end (StartReportDateTime and EndReportDateTime) must be passed without value (blank)
  • The integration follows the rules and triggers defined by customers. Example: The start and end date/time are not mandatory, but the customer can define the obligatoriness through dictionary making tags to be filled out.
  • If is integrated to Shop Floor SIGASFC, it must save tables in this system. The base will be the process of Annotation Model 2, SFCA316
  • O subproduto é tratado na The subproduct is handled in the ListOfWasteAppointments, tags ScrapProduct e and ScrapProductTo. As movimentações dependem da parametrizaçãoThe movements depend on the parameterization(F12) do MATA685, que indica se consome o produto origem ou não. Não é obrigatório digitar os produtos refugados refugo gerado. Neste caso vai registrar somente os defeitos.
    Para que o subproduto seja gerado o parâmetro MV_DIGIPER, deve estar setado como of MATA685, indicating whether the origin product is consumed. Do not enter scrapped products generated scrap. In this case, register only the defects.
    For the subproduct to be generated, the parameter MV_DIGIPER, must be set as 'S'.Para o Reaproveitamento, o Refugo gerado deverá ser o mesmo produto da ordem. Nesse caso o que vai mudar será somente o depósito, onde existirá um local próprio para armazenar o refugo. Esta funcionalidade é para
  • empresas que reaproveitam o produto acabado com defeito (sem gerar subproduto) na composição de outro produto.Para este caso o depósito do refugo poderá ser parametrizado no PCPA109. As movimentações dependem da parametrização For Reuse, the generated Scrap must be the same product of the order. In this case, only the deposit will change, in which there will be a own location to store the scrap. This functionality is for companis that resue the finished product with defect (without generating subproduct) in the composition of other product. For this case, the deposit of the scrap can be parameterized in PCPA109. The movements depend on the parameterization (F12) do MATA685. Se esta parametrização estiver como 'S'  a rotina irá baixar o saldo do produto/local origem e acrescentar/gerar o saldo do produto/local destino. Se estiver como 'N' só irá atualizar o saldo do produto/local destinoIf this parameterization is 'S' the routine will download the balance of the product/origin location and add/generate the balance of the product/destination location. If 'N', it will only update the balance of the product/destination location.

This message is generated by PC-Factory and sent to Protheus.

• • The search can happen as follows:
    Per Product: It returns information of all location of product stock.
    By Stock Location (Warehouse): It returns information of all products in stock location.
  • By Stock Location (Warehouse) and Product: It returns information on Product of Stock Location defined.
    For other fields, Batch, Sub-Batch, series number, location and validity date consider only if you enter product code. If you send these fields without the product code, it must return error message.
  • The Request may be a request list.

• It registers the movement had origin in integration with PC-Factory. The field SD3.D3_OBSERVA is saved as content "TOTVSMES".
• If tag InputOrOutput is I (input) it must execute routine MATA250. If O (output), it executes the process of routine MATA240. Different than I or O, reject message.
• The tag InputOrOutput indicates if it is input or output. Based on this information, consider the type of movement of register PCPA109, folder MOVEMENTS. If input, use field OE_VAR1. If output, use field OE_VAR2.
• No option of reversal. To execute a reversal process, it must send the opposite movement, that is, to reverse an input, it must send an output movement.
• For tag ProductionOrderNumber, it is validate if content is production order (SC2), If OP saves in field SD3.D3_OP, otherwise, saves in field SD3.D3_DOC.
• When Shop Floor is in use, the routine does not allow to execute movement of manual input. Only annotation through Shop Floor.

• It is registered that its origin transfers was through integration with  PC-Factory. The field SD3.D3_OBSERVA is saved as content "TOTVSMES".
• For transfers, routine MATA261 is executed.
• No option of reversal. To execute a reversal process, it must send the opposite movement, that is, to reverse a transfer from X to Y, it must send a transfer movement from Y to X.