Histórico da Página

• If it is an undefined type, it must be saved as GENERIC. Example: Type = SAMPLER.
• The tag StockControlType can be, 1=Serial;2=No. of Series;3=Lote;4=Reference. If field B1_RASTRO is S=SubLote or L=Lote, save as '3'. If field B1_LOCALIZ is S=Yes, save as 2. The product can control lot and series at the same time, being registered in the tags TRIAL and BINCONTROL.
  
  

• The tag ActivityType (Operation Type) is generated with fixed value '1';
• The tag ActivityType (Time Unit Type) is generated with fixed value '1';
• The tag ListOfPertOrders is not generated for Protheus;
• In the deletion of a script, do not delete if there is integrity with the routine of OPERATIONS x COMPONENTS, MATA637. In this case, you do not need to send any message to PC-Factory;
• When adding, editing or deleting data from MATA637, structure message is sent, ItemStructure.

• When updating new balance in ERP, message is sent to PC-Factory.
  Transactions generating movement of stock and executing balance updating routines activating integration:
  Inbound Inv.  - Function B2ATUCOMD1
  Sale Inv. - Function B2ATUCOMD2 Internal Transac. - Function B2ATUCOMD3
• When the balance is updated by an update of PC-Factory do not generated the balance updating message. When the origin of the balance change is TOTVSMES, message is not generated.
  In production annotation message, tag Product Name indicates what is sent to record. For TOTVS MES, this information is saved in SH6.H6_OBSERVA = 'TOTVSMES'.
  If the movement is internal, it is registered in SD3.D3_OBSERVA = 'TOTVSMES'.
• The field QuantityUpdated corresponds to the updated quantity, that is, quantity being moved. 
• The field InputOutput indicates if the movement is input or output. 
• When the item controls address (B1_LOCALIZ), the balance message must be generated only in the confirmation of MATA265, routine executing the address.
• The routines of initial balance of PCP and Stock, MATA220 and MATA805 also generated the balance message.

• • When no is integrated with Shop Floor, MV_INTSFC equal to '0' the scrap is registered in generic table SX5. 
  • It must search in SX5 table according to command below:
    select X5_CHAVE from sx5990 where X5_TABELA TABLE = '43'
    Where:
    - Code of reason is X5_CHAVE
    Table of reason is '43'.
  • When it is integrated with  Shop Floor, MV_INTSFC equal to '1' is generated only the table of  Shop Floor - CYO. Routine SFCA003. If in the message there is no indicator of scrap or rework, consider scrap (CYO_LGRFMP = 'T').
  • Waste reasons have different sizes in tables. Validate it if receipt code does not exceed the size of columns in Protheus.
  • When uses the SIGAPCP it must validate a SX5.X5_CHAVE and SBC.BC_MOTIVO.
  • When uses the SIGASFC validate against the CYO.CYO_CDRF, CY0.CY0_CDRF  and SBC.BC_MOTIVOREASON.

• • When no is integrated with Shop Floor, MV_INTSFC equal to '0' the stoppage reason is registered in generic table SX5. 
  • It must search in SX5 table according to command below:
    select X5_CHAVE from sx5990 where X5_TABELA = '44'
    Where:
    - Code of reason is X5_CHAVE
    Table of reason is '44'.
  • When it is integrated with  Shop Floor, MV_INTSFC equal to '1' is generated only the table of  Shop Floor - CYN. Routine SFCA004. 
  • Stoppage reasons have different sizes in tables. Validate it if receipt code does not exceed the size of columns in Protheus.
    When it uses the SIGAPCP it must validate against the SX5.X5_CHAVE and SH6.H6_MOTIVOREASON
    When it uses the SIGASFC validate against the CYN.CYN_CDSP, CYX.CYX_CDSP and SH6.H6_MOTIVOREASON
    
    

• • 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

• • The co-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 the tag UsedQuantity 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.