Ansicht
Dokumentation

BAPI_MNFCTCONFRCVR_RCVINLUW - Receives Backflush from APO

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CL_GUI_FRONTEND_SERVICES - Frontend Services  
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 in 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).

Exactly one header record must exist for each backflush. The header records are found in table parameter IT_APOHEADS (see below). The header records contain information about the orders, account assignments, backflush entry data, reporting point and the line as well as the quantity. Each backflush must be carried out at 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 using field HEADID. The component list lists materials (assemblies and components), logical information, an indicator for the goods issue, and account assignment information based on components and quantities. Warning: If the component list contains entries for which no header record in table IT_APOHEADS exists , the backflushes will either not be posted at all depending on the constellation, or will be incorrectly posted to another backflush.

Example

You have a line with 3 reporting points. At reporting point RP1, components C1 and C2 are assembled, at reporting point RP2, the component C3 and the semi-finished product S1, which is withdrawn from individual customer stock and is posted immediately, are assembled. At the third reporting point RP3, a final inspection is carried out and the goods receipt for assembly A1 is posted.

At the first reporting point, 5 and 3 pieces are backflushed, at RP2, 2 pieces are backflushed and at reporting point RP3, 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 SLORD

CA76D2 BBAA33 RP1 A1 0001 AA01

5.0 4711

CA76D3 BBAA33 RP1 A1 0001 AA01

3.0 4711

CA76D4 BBAA33 RP2 A1 0001 AA01

2.0 4711

CA76D5 BBAA33 RP3 A1 0001 AA01

1.0 4711

CA76D6 BBAA33 RP3 A1 0001 AA01

1.0 X 4711

IT_APOCOMPLISTS:

HEADID MATERIAL GOODSMOVE_IND SYNC_IND CONFQUANT

SOBKZ

CA76D2 C1 0 _ 10.0 4711

CA76D2 C2 0 _ 15.0 4711

CA76D3 C1 0 _ 6.0 4711

CA76D3 C2 0 _ 9.0 4711

CA76D4 C3 0 _ 4.0 4711

CA76D4 S1 0 X 2.0 4712 X

CA76D5 A1 1 X 1.0 4711

CA76D6 A1 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.

The aggregation of backflushes can improve the performance. 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. 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 backflush.

Parameters

IT_APOACTLISTS
IT_APOCOMPLISTS
IT_APOHEADS
RETURN

Exceptions

Function Group

10507

General Material Data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 5668 Date: 20240606 Time: 051842     sap01-206 ( 102 ms )