Community WIKI SAP Community Welcome, Guest Login Register Search the Community
Customizing
SPRO path: Sales and Distribution → ForeignTrade/Customs → Documentary Payments
Basic Settings:
This definition is used for the creation of a financial document. Generally, only "Letter of Credit" (value '01') is used.
These functions are used in the definition of the LOC master record (subscreen "Banks").
SAP Help: About Documentary Payments (incl. meaning of different bank functions)
These texts are inserted in the definition of the LOC master record (subscreen "Texts").
(D) Define Documents to be presented (VX57 - T607D)
These documents are used in the definition of the LOC master record
These entries correspond with selection of status 'E' in the financial document.
The Financial Document Indicator defines the attributes of the LOC master record. Doubleclick on value '01' for details.
(G) Define Bank Indicators for Financial Documents (VX56 - T607K)
The bank indicator defines the attributes of the bank data used in the LOC master record.
Relationships
Combination of FD indicator (F) + Documents (D) defines: required number of originals and copies of an document
Combination of FD indicator (F) + Bank Function (B) defines: which bank function is used as "Opening bank"? Which bank is a "one time bank" (no master record necessary)?
Combination of Financial Document Type (A) + Financial Document Category defines: which FD indicator (F) and bank indicator (G) is used for this combination.
Regard: Combination of FD type and FD Category needs to be specified when a financial document is created (transaction VX11N).
The Financial Document Category is defined by the system: see values for domain AKKTP.
Risk Management for Financial Documents
A "Forms of Payment Guarantee" determines a permitted combination of: "Payment Guarantee Category" / "Financial Document Category" / "Financial Document Type"
Only "Payment Guarantee Category" = '0' ("Financial Document") is relevant for LOC handling.
Document Determination Schema (L3) is assigned to the relevant sales order types.
Combination of Customer Determination Schema (L2) + Document Determination Schema (L3) determines payment guarantee procedure (L1)
In other words: if a sales order is created customer (sold-to party) and sales order type determine the relevant payment guarantee procedure (transaction VA03: Goto → Header → Billing → block
"Risk Management" → field "payment guarantee procedure").
Every order item category relevant for credit management ((including LOC) has to be flagged
Customizing In a nutshell
Customizing defines:
Document Determination Schema (L3) + Customer Determination Schema (L2) = Payment Guarantee Procedure (L1)
Payment Guarantee Procedure (L1) → Payment Guarantee Forms (K) → permitted kind of Financial Documents (defined by Financial Document Type (A) and Financial Document Category)
Financial Document Type (A) + Financial Document Category = Financial Document Indicator (F) and Bank Indicator (G)
Financial Document Indicator (F) defines the attributes of a financial document (except bank data), created with VX01N
Bank Indicator (G) defines the attributes of the bank dfata used in a financial document
3 options:
1.SAP Menu: Logistics → Sales and Distribution → Foreign Trade/Customs → Payment Guarantee → Documentary Payments → Financial Document → Create
2.Transaction VX11N
3.directly whilst sales order processing: Goto → header or item → billing → extras → financial document → create
(internally: call of VX11N. The financial document category and financial document type defined by the first form of payment guarantee (K) of the specified payment guarantee procedure are used as a
default proposal)
3.company code
1. and 2. determine the "look" of the financial document according customing settings.
The status of the financial document must be set to status ‘ D’ so it can be used in sales orders.
Partner data
• Customer
• Ship-to Party
General data
These are the data of the "Opening bank". They are also available on subscreen "Banks"
block "Values"
Dates/Delivery Dates
block "Deadlines"
• Request date
• Date of receipt
• Last shipping date
• validity end date
opening date
• Latest date of ocean bill of lading (German: "Spä testes Datum des Bordkonnossments")
• Presentation date (German: "Einreichungsdatum")
• Number of days for submitting the documents to the bank
Documents
Corresponds with Customizing Setting (D). Furthermore, customizing (F) determines if more documents may be inserted.
Banks
List of available banks corresponds with Customizing Setting (B) and (F).
To maintain data select kind of bank on the left side, then click on button "Assign Banks". Now it the bank data can be maintained.
• bank function / description / bank country / bank key / External financial doc. no.
Texts
Status
block "Status"
The values displayed on the popup screen when status 'E' is selected correspond with Customizing Setting (E)
Administration
Important field: Credit Status (Goto → Header → Status → block "Processing Status")
Assignment
• Assigning has to be done manually in the order on header or item level (different to the assignment of a export license in SD-FT-CON)
• Assigning can be done on header level (Goto → Header → Billing → block "Risk Management" → field "Financial Document Number") or on item level (Goto → Item → Billing → block "Risk
Management" → field "Financial Document Number")
• If the financial document is assigned on header level it is valid for all items relevant for credit management
• Financial Document Number of a sales document is stored in database table VBKD.
Check
• If no financial document number is assigned credit status is set to 'not approved' (= Check is NOT OK)
• Rej ected items are not relevant (note 833417)
• System checks if the assigned financial document fulfills the necessary requirements: (values, dates, payer data etc.)
• If the check is OK:
Remarks:
• Either the whole value of a sales order can be covered by the financial document or nothing! (Regard: "Credit Status" is a header field)
• Return Process is not possible! (note 1650147)
Protocol
Goto → Header → Billing → Extras → Financial Document → Log resp. Goto → Item → Billing → Extras → Financial Document → Log
Protocol is created dynamically, i.e only when LOC check is processed. Because LOC check is processed during saving it is not possible to display a protocol.
LOC Check is processed when the order is saved. In case the check is negative an information window (popup) is displayed. For more information click on the icon on the popup screen
Delivery Note
The Financial Document number is stored in the delivery header data (table LIKP, field LCNU M) and it is not changeable.
Invoice Document
No LOC check is processed. The Financial Document number is stored in the invoice header data (table VBRK, field LCNU M).
Transactions
(Nearly) all important transactions are accessible via the LOC Cockpit (transaction ENLO) including the following transactions (et. al.):
Data maintained when financial document master data are created/changed via VX11N / VX12N
VBKD-LCNUM
LIKP-LCNUM
VBRK-LCNUM
VBUK-CMGST
= B - blocked
VBAP-ABFOR
S131
U ser-Exits
The LOC check program itself doesn't provide any user-exit, i.e. check cannot be manipulated by user-exit coding.
License master data can be expanded by user-exit to maintain additional fields on a subscreen:
name usageusa
name usageusa
Important programs
Function modules:
RV_ LOC_ CHECK_ ORDER_ LINE_ ITEM - LOC check called at sales order
RV_ LOC_ CHECK_ DELIV_ LINE_ ITEM - LOC check called at delivery note (internal call of RV_ LOC_ CHECK_ ORDER_ LINE_ ITEM)
Modulpool:
Report:
ZVU PDATE_ S131 - correction report for table S131 (no official use, provided in note 597283)
FAQ
some prerequisites necessary in the customizing of the Credit Management area (SD-BF-CM) -> see note 18613
Debugging
Check financial document
A = Check: OK
B = Check: NOT OK
Update Debugging
Regard: Switch on in dialogue! (To be sure: set breal and watch points again even if set before)
value = confirmed quantity * credit price ( trx V/08 calculation procedures: -> control: column ‘ subtotal’ marked with A’ )
G2: credit memo (related to F2 invoice) - not permitted! OLIKW is never decreased!
For Credit/Debit Memos the use of Credit/Debit Memo Requests is mandatory! (note 1650147)
The total of OEIKW + OLIKW + OFAKW must be GREATER EQU AL zero. Otherwise: serious problem!
Find solution:
ad 1.
• error message EI 558 "Financial document values are negative → note 1650147
• open value is wrong → see ad 3. The open value is calculated from the S131 values.
ad 2.
ad 3.
• run report ZVU PDATE_ S131 in test mode (note 597283 ) to check S131 values for a financial document:
Values are not OK: check user-exits, e.g. xxx orMV50AFZ1 (delivery note):
Frequent bug: field U PDKZ of an internal X table (e.g. xvbap, xlips) is changed, e.g. from '_ ' to 'U ', even there isn't a corresponding entry in a Y table. This way, the new value (xtable) is written
to S131 without decreasing the former value (ytable).
ad 4.
ad 5.
note 718260
Dictionary
English Deutsch