启用生产工单标准日志

You cannot activate the creation of change documents for production orders and process orders.
Customizing table T399X (parameters dependent on order type) contains field FLG_DOC but you cannot maintain it using the Customizing transactions for production or process orders.

Production order, process order
T399X-FLG_DOC
SPRO, BADI

It is not intended to use the SAP standard tool for the creation of change documents for production or process orders in the SAP standard system. The indicator in table T399X is only interpreted by maintenance orders and networks.
The reason for this is that the tool cannot determine dependencies of changes and thus would log too many changes that would have a negative effect on the runtime.

Example: A production order contains 10 operations and 1000 components

• Case 1: You change the requirements quantity for a component manually.

           The system creates a change document for the changed component.

• Case 2: You change the planned quantity in the order header manually.

           The change causes that the quantites are changed automatically for all operations and components. The system would create

• • a change document for the changed header quantity,

• • ten change documents for the automatically changed operation quantities (if defined) and

• • thousand change documents for automatically changed component quantities.

Use the SAP enhancement PPCO0007  that is processed when you save order changes. You can find the SAP enhancement in Customizing under the menu path "Shop Floor Control or Production Planning for Process Industries -> Process Order -> System Modifications -> Enhancements for Order Maintenance -> Enhancement when Saving an Order (Header Fields)".
Here you can define additional logic to decide whether or not the system creates change documents.
For this, you can access either the SAP standard tool for creating change documents or your own tool.

The call of the customer exit takes place in function module CO_ZV_ORDER_POST when you save. The current data of an order header is supplied via parameter HEADER_IMP. For collective orders the exit can be called several times - once for each order in the collective order.
Remember that a dialog box must not be accessed and a message must not be issued from the exit.

You can use the attached source code as a template for accessing the creation of change documents.
You can also see in the source code how the current and original data of the different order objects can be provided by internal tables.
The example source code uses function module ORDER_WRITE_DOCUMENT that logs - for the ORDER change document object - the changes for the tables transferred to the module.
It may be appropriate to define a separate object for change documents for orders, for example ZZORDER. If required, you can use the ORDER standard object as a template.
The following tables of the order may have to be taken into account for this type of change document object:
           Table       Description                        Production Process order

• AFAB        Relationships                                        X

• AFFH        Production resource/tool                  X

• AFFL        Work order sequence                      X          X

• AFFT        Process instructions                                X

• AFFV        Process instruction values                          X

• AFKO        Order header data PP                      X          X

• AFPO        Order item                                X          X

• AFVC        General operation                        X          X

• AFVU        User-specific data operation              X          X

• AFVV        Quantities/dates/values in the operation  X          X

• AUFK        Order header general                      X          X

• DRAD_PORDER Link: Document to order                   X

• MLST        Trigger point                            X

• RESB        Reservation                              X          X

• RSDB        Index reservation/direct procurement      X          X

Important:
The creation of change documents using the SAP standard tool requires that the indicator for change document creation is set for the data element that defines the affected table field. For example, this indicator is not set for data element GAMNG (total order quantity) in the standard system which is the reason why changes to the planned order quantity of the order header are not logged. The reason for this is that the GAMNG field of the AFKO table is defined using data element GAMNG.

To be able to set the indicator for the creation of change documents without modifications and display change document data at a later stage, refer to Note 394887 (Enhancements for installing PH-ELR_100_46C) for Release 4.6C; as of Release 4.70 (SAP Enterprise), the Add-On is part of the R/3 standard system.
You can of course set the indicator for activating the creation of document changes manually for each data element using Transaction SE11, however, this changes the data element.
You can display the change documents using, for example, programs RSSCD100, RSSCD150, or RSSCD200. The display from the standard transactions of the order is not supported.
For Release 45B to 46B, you must also create function module CO_BR_AFFX_GET_TABLES_POST in function group COBR using Transaction SE37. Define the following TABLES parameters for the interface:
Parameter name        Type spec.      Reference type    Optional EXP_AFFT               LIKE            AFFTB
EXP_AFFV               LIKE            AFFVB

To be able to archive the generated change documents, you must implement the program modification from Note 508212 in your system.

This note provides an example implementation with which only the following changes can be logged.
- The priority in the order header changes
- The planned quantity of the components changes
- The planned batch of the components changes
- New components are added
- A component is deleted
If you want to log other actions, you must enhance the example implementation yourself.