Document structure/ control


1) A document is saved for every posting. Every Document is uniquely identified by the Document Number, Company Code and Fiscal Year.

2) A Document contains Document header + 2 to 999 line items.

3) Document Type : Controls the Document header and classify the business transactions to be posted.

>> Posting Key : Controls the Line items.

4) Document types are defined at client level. Document types define the following:

a) Number ranges for Document number.

b) Account types permitted for postings. And also

c) The field status of “document header Text” and “Reference number” in the Document header.

d) Whether the invoices are posted with net procedure.

5) Standard Document types are :

KR – Vendor Invoice DR – Customer Invoice.

KG – Vendor Cr.Memo. DG – Customer Cr.Memo.

KZ – Vendor Payment DZ – Customer Payment.

AB – General Document SA – G/L a/c posting.

6) Document numbers can have internal or external number assignment.

7) Up to a future fiscal year – Number range will continue irrespective of year end.

For each fiscal year – At the start of a new year the system starts the number assignment again at the start of the number range. (You need to define number range for every new fiscal year)

8) The document number range must not over lap.

9) Document type AB allows postings to all account types.

10) One number range can be assigned to several document types.

11) Posting keys are defined at client level.

12) Posting keys control:

i) On which type of account the line item can be posted to

ii) The item is posted as a Debit or Credit.?

iii) The field status of additional fields.

In addition to this posting key specifies the following:

>> Whether line item is connected to payment transaction or not.

>> Whether posting is sales relevant.

13) Document line item fields are controlled by :

a) G/L Account specific field status group assigned to the G/L account while creating. (Account specific field status groups are summarized under field status variant which is assigned to company code) If the document is posted to a sub ledger a/c, the field status group of the reconciliation a/c is used.

b) Posting key specific field status group.

(The field status HIDE cannot be combined with the field status REQUIRED entry which causes an error.)

14) Document type does not have default posting key or vise versa. For each FI transaction (E.g. Invoice, Credit memo, Out going payment) you can define a document type and default posting key at:


IMG:FI A/cing>F.A.Global Settings>Document>Default values for document processing>Default values.

(E.g. When posting outgoing invoices, you use the document type "DR" and

posting key "01". You can store these specifications in the system. They

are proposed by the system when you call up the corresponding

transaction).

Comments

Post a Comment

Popular posts from this blog

Batch input session SM35

Image
Batch in put session is the same for all the modules and processes. Its independent and it can be use for all the processes. In SM35, we can select the session for recurring entry or for any other scheduled process. We can manage sessions, lock it, unlock it, see logs etc. For running batch input session it gives us 3 options. Foreground, background and errors only. Foreground means system will roll all the transaction on the screen and we can see it. Background means system will process all the transaction in background. Errors only means the system will process in background but will show errors. For ease we select extended log and expert mode while starting a batch input session. Now once we run batch input session we need to know results of it right? Here it is how we get results of batch input session in SAP FICO.  Batch job overview
Read more

Manual Clearing Vendor open line items F-44

Image
In SAP FICO, F-53 kept the line items open even if it got paid. How to clear them? Through F-44. Here give the vendor account number whom we want to clear line items. Process open items will redirect to the new screen. Select which line items to be cleared, simulate and save. It will clear the line items and gives a document number. Upon displaying document it shows a document with no line items but just header data. It is an important certification question that only clearing document display have just header data and no line items. All the financial accounting entries saved in tables BKPF and BSEG for header data and line item data respectively. So for most of the documents there is a link between these two tables, but for clearing document there is an entry in BKPF only.
Read more

iDoc types and applicable message types

Outbound processing: BENREP     BENEFIT1 CARNOT    DELVRY01 CREADV     PEXR2001, PEXR2002 DEBADV     PEXR2001, PEXR2002 DELFOR     DELFOR01 DELINS     DELFOR01 (FDS and JIT) DELJIT     DELFOR01 DESADV     DELVRY01, DELVRY02, DELVRY03 (previously: DESADV01) EXPINV     EXPINV01, EXPINV02, EXPINV03 GSVERF     GSVERF01 IFTMIN     SHPMNT03 IMPINV     IMPINV01 INVOIC     INVOIC01 ORDCHG     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 ORDERS     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 ORDRSP     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 PAYEXT     PEXR2001, PEXR2002 PRICAT     PRICAT01 PROACT     PROACT01 QUOTES     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 REMADV     PEXR2001, PEXR2002 REQOTE     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 SHPADV     SHPMNT03 SHPMNT     SHPMNT01, SHPMNT02, SHPMNT03, SHPMNT04 SHPORD     DELVRY01 WHSORD    DELVRY01 Inbound processing: CREADV  
Read more