Ansicht
Dokumentation

BAPI_MNFCTCONFRCVR_RECEIVE - Receives Backflush from APO

BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Functionality

You can use this function module to transfer one or several backflushes to the R/3 System. In R/3, the information is then saved on the database. Depending on the process and setting in the material master record accessing this BAPI triggers the posting of material movements (stocks) and costs in R/3. Other components can be posted later (asynchronous) using transaction PPCGO in R/3 (aggregated).

For each backflush, exactly one header record must exist. The header records are in Table parameter IT_APOHEADS (see below). In the header record is information on the orders, account assignments, backflush entry data, reporting point and the line as well as the quantity. Every backflush must be carried out for a reporting point. A goods receipt is indicated in the component list.

Material movements are usually also posted for a backflush. These are recorded in table parameter IT_APOCOMPLISTS. The entries in the component list are assigned to a header record via field HEADID. The component list lists materials (assemblies and components), logical information, an indicator for the goods receipt, account assignment information based on components and quantities. Warning: If the component list contains entries for which no header record exists in Table IT_APOHEADS, depending on the constellation, the components are not posted or are posted incorrectly to another backflush.

Example

You have a line with 3 reporting points. At reporting point Z1, components K1 and K2 are assembled, at reporting point Z2, the component K3 and the semi-finish product H1, which is withdrawn from individual customer stock and is posted immediately, are assembled. At the third reporting point Z3, a final inspection is carried out and the goods receipt for assembly B1 is posted.

At the first reporting point, 5 and 3 pieces are backflushed, at reporting point 2, 2 pieces are backflushed and at reporting point Z3, you post 1 GR and 1 piece as scrap.

All backflushes are transferred to R/3 at once. The transfer then is as follows (simplified!):

IT_APOHEADS:

HEADID ORDERID REPPOINT HEADMATNR VERSION LINE_HEADER

CONFQUANT FLG_SCRAP KDAUF

CA76D2 BBAA33 Z1 B1 0001 AA01

5,0 4711

CA76D3 BBAA33 Z1 B1 0001 AA01

3,0 4711

CA76D4 BBAA33 Z2 B1 0001 AA01

2,0 4711

CA76D5 BBAA33 Z3 B1 0001 AA01

1,0 4711

CA76D6 BBAA33 Z3 B1 0001 AA01

1,0 X 4711

IT_APOCOMPLISTS:

HEADID MATERIAL GOODSMOVE_IND SYNC_IND CONFQUANT KDAUF SOBKZ

CA76D2 K1 0 _ 10,0 4711

CA76D2 K2 0 _ 15,0 4711

CA76D3 K1 0 _ 6,0 4711

CA76D3 K2 0 _ 9,0 4711

CA76D4 K3 0 _ 4,0 4711

CA76D4 H1 0 X 2,0 4712 X

CA76D5 B1 1 X 1,0 4711

CA76D6 B1 1 X 1,0 4711

Notes

A backflush always refers to a version of a line/reporting point structure. This information has to be passed on to the R/3 system before the first backflush for this production line. To do this, use the module BAPI_MNFCTCONFRCVR_RPV_RECEIVE.

GUIDs (Global Unique Identifier) are used for many keys. A GUID is multi-system and is time specific. They are created with special function modules. The majority of GUIDs are of CHAR32 format. The format, however, is hexadecimal. That is, you can only use characters 0..9 and A...F.

Aggregating backflushes can improve performance as buffer mechanisms can be used. This is especially advantageous when data is used again (for example, the same components and so on). However, when backflushing a large number of backflushes (100, for example), memory requirement increases significantly and performance becomes poorer again.

Authorizations:

A special authorization object exists for production backflushing with BAPIs. It is called C_BCKFLUSH and has fields ACTVT and WERKS. The following activities exist:

- 31: Backflush

- 24: Archive

- A8: "Process mass data". This means triggering the aggregated goods withdrawal. (Transaction PPCGO)

The authorizations for MM and so on must also be maintained. Please check in SU22 under transaction MFBF which objects you have to check.

Further information

Refer also to the application documentation, especially the technical appendix for production backflushing.

Parameters

IT_APOACTLISTS
IT_APOCOMPLISTS
IT_APOHEADS
RETURN

Exceptions

Function Group

10507

BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5649 Date: 20240523 Time: 152205     sap01-206 ( 106 ms )