SAP Note

390635 - Change documents for production and process orders

Component: PP-SFC-PLN (Order Planning), Version: 24, Released On: 01.03.2024

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

Other Terms
Production order, process order, change document, CDHDR, CDPOS
T399X-FLG_DOC
SPRO BAdI

Reason and Prerequisites

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 the table T399X is
interpreted only 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 which 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 the quantites to be 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.

Solution
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 an additional logic to decide whether or not the system should create
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 the function module CO_ZV_ORDER_POST when you
save. The current data of an order header is supplied via the 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 the function module ORDER_WRITE_DOCUMENT that logs - for the
change document object ORDER - 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 standard object ORDER 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 order 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
the change document creation is set for the data element that defines the affected table
field. For example, this indicator is not set for the 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 field GAMNG of
the table AFKO is defined using the 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 SAP 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, the program 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 the function module CO_BR_AFFX_GET_TABLES_POST
in the 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 SAP Note 508212 in your system.

This SAP 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.
- A new component is added.
- A component is deleted.
If you want to log other actions, you must enhance the example implementation yourself.
 Attributes
Key Value

Other Components PP-PI-POR (Process Order)

Other Components PP-SFC-PLN-HEA (Header / Operation)

Other Components PP-SFC-PLN-CPT (Components)

Modification the note contains a modification

Transaction codes CLEAR

Transaction codes SE11

Transaction codes SE37

Transaction codes SPRO

Transaction codes AFAB

Transaction codes CODC

Software Components
Software Component From To And subsequent

SAP_APPL 45B 45B

SAP_APPL 46A 46B X

SAP_APPL 46C 46C X

SAP_APPL 470 470 X

SAP_APPL 500 500 X

SAP_APPL 600 600 X

SAP_APPL 602 602 X

SAP_APPL 603 603 X

SAP_APPL 604 604 X

SAP_APPL 605 605 X

SAP_APPL 606 606 X

SAP_APPL 616 616

SAP_APPL 617 617

SAP_APPL 618 618

S4CORE 100 100

S4CORE 101 101

S4CORE 102 102

S4CORE 103 103

S4CORE 104 104

S4CORE 105 105

S4CORE 106 106

S4CORE 107 107

S4CORE 108 108

SAP_BASIS 46D 46D

Correction Instructions
Software Component Number of Correction Instructions

SAP_APPL 2

S4CORE 1
 This document refers to
SAP Note/KBA Component Title

806119 PP-SFC Saving order processing logs

508212 PP-SFC-CPL Modif: Archiving change documents for production order

428320 PP-SFC Table AFVC_BT_OLD is not filled

394887 BC-UPG-ADDON Enhancements for installing PH-ELR 100_46C

36240 PP-SFC Change documents for production orders

32524

This document is referenced by

SAP Note/KBA Component Title

3417782 Enable CGTO Custom Screen for Process Order Transactions in SAP GUI

508212 PP-SFC-CPL Modif: Archiving change documents for production order

394887 BC-UPG-ADDON Enhancements for installing PH-ELR 100_46C

806119 PP-SFC Saving order processing logs

428320 PP-SFC Table AFVC_BT_OLD is not filled

36240 PP-SFC Change documents for production orders