|
Functionality
You are backflushing for the make-to-order scenario. If the backflushis not successful, the system displays an appropriate message via theexporting parameter RETURN. If the backflush is carried outsuccessfully, the exporting parameter is filled with initial values.
The backflush is carried out for a sales order. Depending on the stockcategory (valuated or nonvaluated), the costs are collected at either aproduct cost collector or for the sales order.
Meaning of the parameters:
BFLUSHFLAGS: Control of the type and scope of a backflush
BFLUSHDATAGEN: Parameter for the backflush data independent of thescenario
BFLUSHDATAMTO: Parameter specifically for the make-to-order scenario
SERIALNR: List of serial numbers
RETURN: Return of an error code if the backflush could not be carriedout successfully
In this module, no COMMIT WORK is carried out.
Note that a COMMIT WORK is created directly after accessing this BAPI.This means that it is not possible to use several backflushing BAPIsthat save data on the database in sequence and then only create oneWORK COMMIT after the last BAPI. Should this happen, however, thesecond BAPI will be terminated as such a chain of accesses is notsupported by the program.
Notes
A sales order and/or a planned order must be transferred.
You must also enter a posting date and a document date.
If the corresponding repetitive manufacturing profile is set so that anonline correction is mandatory in the event of withdrawal errors and ifwithdrawal errors occur in the backflush, the backflush cannot becarried out and an appropriate error code is recoded in the RETURNparameter.
If the corresponding repetitive manufacturing profile is set so that anonline correction is optional in the event of withdrawal errors and ifwithdrawal errors occur in the backflush, the system createsposprocessing records for the components which could not be withdrawn.
Therefore, make sure that the creation of postprocessing records isallowed in the repetitive manufacturing profile. Otherwise, thewithdrawal errors are not logged and a system-supported postprocessingis not possible.
The backflush number given by the system is returned to the caller viathe parameter CONFIRMATION. Description
The backflush number is given by the system when carrying out thebackflush. It specifically identifies a backflush within the SAP system. Description
The fields of this parameter provide information on the error whichoccurred when the backflush could not be carried out successfully. Thefield MESSAGE contains a detailed description of the error should theshort text of the error not provide enough space to describe the reasonfor the error. Description
The individual parameters of this structure contain the data requiredfor the backflush independent of the selected scenario (process). Thefollowing parameters must always be transferred:
POSTDATE,,,,Posting date
DOCDATE,,,,Document date
The fields PROD or PLANPLANT must be filled. Depending on whether youare backflushing a yield quantity or a scrap quantity, you must fillone of the fields, BACKFLQUANT or SCRAPQUANT.
The field, PLANORDER must be filled if the backflush is to be carriedout specifically for a planned order. Description
The individual parameters of this structure contain the data requiredfor the backflush specifically required for the make-to-order scenario.These are the following parameters:
SORDER,,,,Sales order number
SORDERITEM,,Sales order item
These parameters must be filled if no planned order is entered in thePLANORDER parameter.
WARNING: If only the parameters SORDER and SORDERITEM are transferredand several planned orders exist for this sales order, the backflushcannot be carried out as the system cannot select one of the plannedorder automatically. In such a case, enter the appropriate plannedorder only or enter the planned order as well as the fields for thesales order. Description
The individual parameters of this structure control the type and/orscope of the confirmation to be posted within the confirmation processchosen via the selection of the BAPI.
- Parameter BCKFLTYPE
This parameter defines the type of confirmation to be posted. In thecase of a confirmation in the make-to-order scenario, the followingconfirmation types are allowed:
01,,Final confirmation
21,,Final confirmation (document-neutral cancellation)
- Parameters RP_SCRAPTYPE, ACTIVITIES_TYPE, COMPONENTS_TYPE
These parameters have no significance in the make-to-order scenario.Description
Goods movements that are to be posted depending on the confirmations.
Automatic goods movements can be posted with a confirmation. Thisinvolves the backflushing of components and automatic goodsreceipt postings for an assembly. If this data is to besupplemented or corrected, the goods movement data can be transferred inthe Goods Movements table.
If a confirmation is assigned to at least one goods movement, there isno determination of automatic goods movements for the confirmation whenthe latter is saved. That is to say, the goods movements passed oncannot be regarded as additional goods movements to the onesautomatically posted. Instead they represent the replacement items forthem so to speak.Default Note
Note that not all of the indicators of the Goods Movements tablecan be used. For example, the NO_TRANSFER_REQ = X indicator is set toprevent the generation of a transfer requirement when the goods movementis carried out. However, this indicator has no effect - a transferrequirement is created nevertheless.
Cause: The inventory management structure BAPI2017_GM_ITEM_CREATE isused to pass on goods movements to confirmation BAPIs. However, thisstructure contains some fields that have no relevance to confirmationsin repetitive manufacturing or are not supported. Generally, thecomplete MM functionality cannot be supported in the posting of goodsmovements via confirmations. This applies both to the confirmationdialog transactions and the confirmation BAPIs.Description
If serial numbers have to be maintained for the finished product to bebackflushed, you use this parameter to transfer the serial numbers to beused for posting the goods receipt of the finished product. Note that,in certain circumstances, the number of serial numbers to be transferredmust correspond exactly to the backflush quantity (this depends on theserial number settings in the SAP system). If in such a case too fewserial numbers are transferred, the backflush cannot be carried outsuccessfully.
|