/FRE/BIF_INB01 - F&R Interface ProcessingFill RESBD Structure from EBP Component Structure Vendor Master (General Section)
This documentation is copyright by SAP AG.
The SAP Forecasting and Replenishment (F&R) interface processing is used to process the data stored in the interface tables (also called BIF tables) and to fill in the F&R data accordingly.
Successfully processed BIF entries will be deleted after processing.
BIF entries, which could not successfully be processed, will be marked as erroneous and remain in the BIF table. The entries which could not be processed as well as the reason why their processing failed can be seen in the Connectivity Workbench (transaction /FRE/CON)
The BIF tables are used to store the data sent from the connected SAP ERP system instead of processing them directly (without storing in BIF tables). The benefit of using the BIF tables is to have more control over the data processing. Starting the SAP F&R interface processing in batch jobs gives you the possibility to process the data at a point in time that best suits your needs.
The SAP F&R interface processing ensures that the data stored in the BIF tables is processed in the right order. (For example, the processing of the location product data will not start before the processing of the location data and the product data is completed.)
In the SAP F&R Customizing settings, you have to define the usage of interface tables for the different interfaces, where each interface is defined by a message type.
Although most of the message types allow the possibilty of direct processing (without buffering the incoming data in interface tables) SAP strongly recommends the usage of the buffering mechanism.
Direct processing is not supported for the following message types and the incoming data will be stored in BIF tables in all cases:
- Location product
- Time series
- Transportation lanes for products
Start transaction /FRE/BIF; you are on a screen containing three tab pages. The three tab pages are are Inbound Message Types, Outbound Message Types and Control Data.
Inbound Message Types:
The screen for the inbound message types is divided into different areas.
The first area gives you the possibility to enter selection criteria.
All other areas indicate which selection criteria is used when you select one of the interfaces offered in this area.
For example: For processing location product data, the selection criteria maintained for product, product type, target location and target location type are used.
The interfaces offered in the last area, are Without Selection Criteria. For these interfaces there is no possibility to define selection criteria and all entries in the BIF tables are processed.
For most of the interfaces you area able to define a maximum number of objects during parallel processing.
This value in not an absolute value but a guideline of how many objects of the relevant interface are
to be processed in one single task during parallel processing. The parallel processing of the BIF entries
of one interface could lead to locking problems in case BIF records for the same objects are processed
in different parallel tasks. Therefore, the real number of processed objects of that interface can be higher than specified in the maximum number for parallel processing.
For some interfaces a parallel processing of the BIF entries is not possible and therefore the field for the maximum number is not offered for them.
If you do not specify a value for the maximum number of the relevant interface in this tab page, the default value for the maximum number which is offered on the control data tab page is used for the interface.
You have to mark the interfaces for the BIF entries you want processed.
For most of the interfaces, only those BIF entries which have status N (indicating Not processed) will be processed .
Entries having another status (for example, Eindicating Erroneous) will not be processed. In order to process these entries, you have to first change their status to N. You can use report /FRE/BIF_INB03 to change the status of the BIF entries.
Exceptions to these rule are the Transportation Lane for Products and the Location Product.
Outbound Message types
Order proposalis the only message type offered in this tab page. This tab page is used to send order proposals created within SAP F&R to the connected SAP ERP system.
The selection criteria offered here can be used to restrict the set of released order proposals which are to be transferred. In case no selection criteria are defined, ALL released order proposals (= status '30') are transferred.
In addition, all entries in the BIF table for outgoing order proposals having status Nare sent to the SAP ERP system. These kinds of entries exist in case BIF entries having status Ehave been set to Nagain using report /FRE/BIF_INB03.
In this case, the selection criteria offered on this tab page does not influence the existing entries in the BIF tables for outgoing order proposals. Therefore, to ensure data consistency, all records in the BIF tables have to be considered regardless of the entered selection criteria.
This tab page must be filled accordingly whenever you want the BIF entries to be processed in parallel mode.
The field Max Tasksspecifies the maximum number of tasks to be processed in parallel.
The field Max.. Number objects (Default)specifies a default value for the maximum number of objects of one interface to be processed during parallel processing. This default value is used during parallel processing of all those interfaces for which no maximum value has been specified by the user on the other tabs pages.
When the field Background processing: Status Canceled in Job Overviewis marked, the processing of those interfaces are highlighted as canceled in the Job Overview (red traffic light), as soon as one of the jobs started in parallel returns an error. The flag is only taken into account if the program was started in a batch job.
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 7363 Date: 20191212 Time: 021851 sap01-206 ( 59 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.