|
Use
Note Every structure is identified by record type and possible table name. The structures are in detail: BGR00 record type 0 session prefix BKN00 record type 1 header data BKNA1 record type 2 general information data BKNVA record type 2 unloading points BKNVK record type 2 contact person BKNBK record type 2 bank data including new bank master data BKNB1 record type 2 company code data BKNB5 record type 2 dunning dates BKNKA record type 2 credit limit is central BKNKK record type 2 credit limit control area BKNVV record type 2 sales area data BKNVD record type 2 messages BKNVI record type 2 taxes BKNVL record type 2 licenses BKNVP record type 2 partner functions For every field which is transferred in batch input structure, you mustbe able to decide whether the value of the field is initial (forexample, the field should be reset to the initial value) or whether nobatch input at all is necessary for this field. This means that a special character must be specified which has thefunction 'no batch input for this field'. This special character is the character '/' by default. If the special character '/' is not to be used, you can specify anotherspecial character in the session prefix in field BGR00-NODATA, whichwill carry out this function. Before filling the batch input structure, every field of the structures(with the exception of the session prefix BGR00) must be prepared forthe beginning of the field with this special character. The fields of the structures refer to data elements of the fields ofthe original tables. However, numeric and packed fields are anexception These need separate data elements of category CHAR for batchinput, since packed fields cannot be preset with a special character. That means that amounts with decimal point can be transferred to theinterface. End of record marker: If a batch input structure is later extended, the new end of thestructure is indicated by a special field (SENDE). If you are alreadyworking with the new, extended structure, you must also supply thisfield with the NODATA indicator when 'initializing' the structure. As aresult, it can be recognized when importing the structure whether thedata is based on the old or the new structure. Special fields in the session prefix: In the session prefix, the batch input session name must be given(BGR00-GROUP). Sending a second session prefix causes the closing ofthe current session and the opening of a further session. In the session prefix, the special character NODATA can be transferred(see above). A block date can be transferred in the session prefix (BGR00-START). Ifthis date is set, it must have the format 'YYYYMMDD'. Programs: The generation program RFBIDEG0 uses the frame RFBIDE01 and writes thecoding contained in it together with the newly generated coding to thebatch input program RFBIDE00. Coding for the 'field transports' is generated by the generationprogram per screen and per input field. Supported transactions: The following central transactions are supported in the presentversion: With the creation and change transactions, transferred block fields ordelete flags are also processed. The system then goes onto theadditional screens provided for this. Block fields can only be processed with block transaction XD05. Delete flags can only be processed with delete transaction XD06. For all bank data to be processed, the structure BKNBK must betransferred. If an existing bank data is to be deleted, the fieldBKNBK-XDELE must be marked. If the bank master data of a bank data is new, the data of this bankcan also be transferred in structure BKNBK. The new bank master dataare then created when processing the session. For every unloading point/contact person/tax/license/message/partnerfunction to be processed, the structure BKNVA/BKNVK/BKNVI/BKNVL/BKNVD/BKNVP must be transferred. If a record is to be deleted, thefield XDELE is to be marked in the relevant structure. For unloading points, it is to be noted that EITHER a goods receivinghours ID (BKNVA-WANID) OR goods receiving hours can be transferred(BKNVA-MOAB1, BKNVA-MOAB2, and so on,) For contact persons, it is to be noted that no partner number isspecified when creating (internal number assignment). If, however, anumber is given, this must not be the same as a number assigned toanother customer (termination). For taxes, only 'valid' records may be transferred, that is,BKNVI-ALAND must be the country of the sales organization or one of theplants belonging to it and BKNVI-TATYP must be allocated to thiscountry via table TSTL. These two fields must be transferred.Furthermore, it is to be noted that the tax classification BKNVI-TAXKDfor the tax category is permitted (table TSKD). When tax data is transferred by batch input, it is to be noted that the data must always be transfered on the step loop screen 1350 of module pool SAPMF02D. This is also the case if there is only one relevant tax record (country/tax category/tax indicator). In this case, screen 1350 would not apply and the tax indicator would be maintained inscreen 0320 (billing). However, in batch input, tax data should not be transferred to screen 0320 under any circumstances as this leads to termination. Screen 1350 is to be included in the procedure directly after screen 0320. Complete data records must be transferred (KNVI-ALAND, KNVI-TATYP und KNVI-TAXKD). It is advisable to look at tax determination and in particular the contents of table KNVI online before constructing the batch input procedure. For licenses, as for taxes, the validity of country and tax category(BKNVL-ALAND, BKNVL-TATYP) are to be checked. Generation of record layouts: You can generate record layouts via the menu bar option "Tools" in theaccounting Customizing menu. Alternatively, you can go directly fromhere into Customizing |