Symptom
Automatic goods movements are not posted.
There is no material document or a planned change record in tables AFRP1, AFRP2 or AFFW or an error record in table AFFW.
Error records for goods movements deleted manually cannot be identified. You can delete them with transaction COGI, for example.
However, error records can also be deleted by canceling the responsible confirmation.
The system should check whether AFFW records are deleted by processing in the background job without corresponding material documents being posted.
Other Terms
COGI, CO13, CO1P
CORUPROC, CORUPROZ, CORUAFWP
Reason and Prerequisites
The disappearance of AFFW records cannot be explained.
Solution
Make a temporary modification to the goods movements update from the confirmation. You should use the modification to localize the cause of the error. After the removal of the cause, you have to deactivate logging again since it might cause performance to deteriorate.
Logging of all AFFW records which are deleted and for which no material document is created.
Note:
- 1. The correction instructions apply only for releases up to and including 4.6C.
For Releases 4.70 and higher, the correction instructions are contained in the standard source code; you only need to activate logging using the modification (see below).
In addition to the changes described in the correction instructions, carry out the following enhancements:
- a) Additional import parameter for function module CO_FW_AFFW_POST
Release 4.6:
Parameter name Type Ref.type Optional Pass value
I_CALLED TYPE CHAR01 X X
Release 4.5:
Parameter name Ref. type Optional
I_CALLED CHAR01 X
- b) Use transaction SE11 to create new database table AFFWPRO.
Attributes
Description : Log of deleted AFFW entries
Development class: CORU
Delivery class: L
Fields
Fields Key Init Field type Ref. table Ref. field
MANDT X X MANDT
AUFNR X X AUFNR
WEBLNR X X WEBLNR
WEBLPOS X X CIM_COUNT
UPDDA X X DATUM
UPDZT X X UZEIT
MATNR MATNR
WERKS WERKS_D
LGORT LGORT_D
CHARG CHARG_D
BWART BWART
ERFMG ERFMG AFFWPRO ERFME
ERFME ERFME
RUECK CO_RUECK
RMZHL CIM_COUNT
ERSDA ERSDA
ERZET ERZET
USNAM USNAM
TCODE TCODE
UPDIND VBKZ
CALLED CHAR01
Technical settings
Data class APPL1
Size category 1
Buffering not allowed X
- 2. Logging can only be activated by a modification. To do this, you must (up to and including Release 4.6C) first implement the changes contained in the correction instructions. After this, delete the following statements in function module CO_FW_AFFW_POST:
- a) Activating logging for deleted AFFW records
clear prot_del_is_active.
- b) Activating logging for changed AFFW records
clear prot_upd_is_active.
System behaviorTable AFFWPRO lists the following AFFW records which can be differentiated by the 'update indicator':
- UPDIND = D: existing AFFW record was deleted
- UPDIND = U: existing AFFW record was updated
Software Component | From | To | And Subsequent | ||
---|---|---|---|---|---|
SAP_APPL | 45A | 45B | |||
SAP_APPL | 46A | 46B | |||
SAP_APPL | 46C | 46C | |||
SAP_APPL | 470 | 470 | |||
SAP_APPL | 500 | 500 |
Software Component | Number of Correction Instructions | ||
---|---|---|---|
SAP_APPL | 3 |
Software Component Version | Support Package | ||
---|---|---|---|
SAP_APPL 46C | SAPKH46C05 | ||
SAP_APPL 46B | SAPKH46B13 | ||
SAP_APPL 45B | SAPKH45B38 |