Tasks to be completed when documenting an SAP Transaction, Report or Message code.1. Title of the page = SAP Transaction code, SAP Report or SAP Message2. Add the following Labels, respectively :
3. On the left section, describe the steps. On the right section, insert respective print screens and additional guidelines, if needed (e.g. Main selections of the transaction...) |
Background:
Creation of the files
The file contains technical information needed for the upload (2 first lines + first column) and the data.
Data are split in 4 categories :
1° the header of the document (technically contained in table BKPF)
2° the line items (technically contained in BSEG)
3º Header and Item Long text (BSEG for Long Text & TTXIT-TDID)
4º Field for attachment of files (BAPI)
Technical information
First line :
- contains the title of the column (this description could be translated - there is no check)
Second line : - contains the SAP technical name of the column.
MANDATORY – MUST NOT BE CHANGED
First column : - The title of the column (second line) must be "ITEM"
- contains the "identification code" of the operation
- MANDATORY - THE SAME CODE MUST APPEARS ON ALL THE LINES OF A SINGLE DOCUMENT.
- If the file contains more than 1 document, the "identification code" must change starting from the first line of the new document
In fact, the technical names can be an any line (not necessarily the second one), but the line with technical names should contain only real technical names.
Technical names of a given field can be displayed in FB01 (or else), <F1> on the field, <Technical Information>)
You can add an additional column with the right technical name at any time. (To make it short, every BBKPF or BBSEG field can be used in a new column).
We can insert comment in line 1 or on any line that begins with a star '*'.
Data
The data start on the third line of the second column with the header data.
Header data :- Co code BKPF-BUKRS
- Transaction codeBKPF-TCODE (always in Upper Case)
- Doc Type BKPF-BLART
- Doc Date BKPF-BLDAT
- Posting Date BKPF-BUDAT
- Posting period BKPF-MONAT
- Currency BKPF-WAERS
-Transfer in doc curr.BKPF-XBWAE (***) (By default "X" = currency rate at the moment of the final posting. If the rate is established at the moment of the "park" enter the value "!" in this field - Reversal reasonBKPF-STGRD (**)
- Reversal date BKPF-STODT (**)
- Reference BKPF-XBLNR
Header Text BKPF-BKTXT
Line item data :
- Co Code BSEG-BUKRS (for cross company posting; never on the first line of the document)
- Posting Key BSEG-BSCHL
- G/L account BSEG-SAKNR
- Amount Doc curBSEG-WRBTR
- Amount Cy CurBSEG-DMBTR
- Tax code BSEG-MWSKZ
- B.A. BSEG-GSBER
- Value date BSEG-VALUT
- Cost center BSEG-KOSTL
- CO Order BSEG-AUFNR
- Croco Partner BSEG-VPTNR
- WBS element BSEG-PROJK
- Profit center BSEG-PRCTR
- Material BSEG-MATNR
- Quantity BSEG-MENGE
- Unit of mesure BSEG-MEINS
- Personnal nr BSEG-PERNR
- Assigment BSEG-ZUONR
- Text BSEG-SGTXT
- Transaction TypeBSEG-ANBWA or BSEG-BEWAR
- Trading Patner BSEG-VBUND
- Reference Key 3 BSEG-XREF3
(Further technical field names could be used...)
Header and Item Long Text (See Section 2.2.3 for more details) : - Item Long Text BSEG_LONG_TEXT
- Header Long Text BKPF_LONG_TEXT
- Both Item and Header Long Text Language TTXIT-TDSPRAS
- Header Long Text ID TTXIT-TDID
"0001" - Correspondence
"0002" – Note (default)
"0003" - Payment advice information
"0004" - Number of Payment Order
The Excel file can handle very complex documents with more BSEG fields, withholding tax, or also clearing (FB05) etc. If needed, ask to SIS.
Automatic attachment of files (See Section 2.2.3 for more details) : - Property of file BAPISIGNAT-PROP_NAME
- Full filename path BAPISIGNAT-PROP_VALUE mandatory fields
(**) only for FBS1 where it is mandatory
(***) By default "X" = currency rate at the moment of final posting.
|
The empty columns can be removed from the file.
Creating a ZZF_posting_file from one or more documents in SAP
If you enter in transaction ZZF_POSTING_FILE_DOWNLOAD you can display one or many existing documents (preferably FB01 ones) in the necessary Excel format for abap ZZF_POSTING_FILE.
Some little changes are needed (in you specify a Customer, no G/L account is necessary). or in short words, we can use ZZF_POSTING_DOWNLOAD to download a document, then modify it (dates...), and upload a new similar one with ZZF_POSTING_FILE.
In fact the download is a display in an Excel file, that we can save on our disk. (If during display you are prompted for a choice of Excel template, use "sap_om.xls")
File preparation
Different templates can be used, depending on the applicability:
Global Posting File - PF1.xlsm
Global Posting File - WP1.xlsm
Global Posting File - WP1 IECRA CO_PA Adjustments.xlsm
Follow the instructions detailed in the User Guide tab of each template. |
Use transaction code:
|
Enter the transaction code ZZF_POSTING_FILE:
Validate with 
.
Fill in the transaction fields
By default, some of the transaction fields are hidden. To view them, press the 
button.
If you press it once, the test run mode filed appears:
If you press it twice, the fields "display mode" and the fields to process the transaction by batch input appears:
Fill in the fields:
- File name: select the file created
- Decimal point format:
- Normally "as entered"
- If an error message appears, regarding the format for all documents, you may select "correct decimal; point, number" and run the program again. Be careful, if some documents are posted, create a new file containing only the documents in error
- Date format:
- Normally "as entered". However, you can also define how the system will read the date in the file if different format than the normal one. The available formats are:
- Display mode:
- Normally "E" (in order to have the most appropriate "error message"
- You may use "A" in order to see all the screens
- Normally "E" (in order to have the most appropriate "error message"
- Test run:
- In case you launch the transaction in test mode, the result will be the following:
- In case you launch the transaction in test mode, the result will be the following:
The error related with the date format appears when the date format chosen is different from the one in the file. to solve the error is only necessary to confirm the date format.
The other error (red bars) is only a warning informing that the field contain more characters than the allowed in SAP field (applicable for Doc. Header Text, Reference, assignment and text fields).
- Call transaction / create batch input:
- By default, the field is flagged on "Call transaction…using…", but there is the possibility to execute this transaction creating a batch input session in SM35. To do this, select:
- By default, the field is flagged on "Call transaction…using…", but there is the possibility to execute this transaction creating a batch input session in SM35. To do this, select:
- And give a name to the batch to be created. When launched, the foreground posting transaction will generate errors stating "Process Cancelled by User", however, these errors should be ignored. The system will create 1 batch input per posting to be performed.
To post the posting file, insert the file to be posted (in excel or txt format):
Launch the transaction
Launch transaction with 
.
If the file to be uploaded is open you will receive the following message:
In this case, close the file and launch the transaction again |
Posted document (FB01 – FB41 - FBS1):
Parked document (FBV1):
If you click on a line, you will access the document:
With transaction FB03 for posted document (created through FB01 or FB41 or FBS1 file):
or 
With transaction FBV2 for parked document (created through FBV1):
In this case, you have to save it as complete in order to "check" and give the "green light" for posting to SBS RtR BO (change RtR BO)
team.
