Tables for Collection, dispute and credit management

Hi SAP Gurus,
I would appreciate if any one could provide the list of tables for collection, dispute and credit management. Thanks!
Regards,
aj

I think you mean the tables for FSCM.
The easiest way to find it is to do SE16 FDM*
FDM_AR_WRITEOFFS               FSCM-DM: Automatic Write-Offs Not Executed
FDM_BUFFER                     Cluster for Decoupling in 1-System Scenari
FDM_BW_INV_DELTA               Delta Queue for BI Invoice Extractor
FDM_COLL_CCOLOAD               Company Codes for which Initial Load Perfo
FDM_COLL_CFIELD                FSCM-COL: Relevant Fields for Document Cha
FDM_COLL_COMPCOD               FSCM-COL: Active Company Codes of Collecti
FDM_COLL_DUNNLEV               Harmonized Dunning Levels
FDM_COLL_LASTPAY               Last Payments of Business Partner
FDM_COLL_LTRIG                 Missing Entries of Table FDM_COLL_STRIG
FDM_COLL_SFIELD                FSCM-COL: Relevant Fields for Document Cha
FDM_COLL_STRIG                 FSCM-COL: Control of Trigger Update in TRO
FDM_COLL_TROBJ                 FSCM-COL: Trigger Table for Collections Ma
FDM_CONTACT_BUF                Personalization of Contact Person Data
FDM_DCOBJ                      FSCM-DM Integration: Disputed Objects
FDM_DCPROC                     FSCM-DM Integration: Dispute Case Processe
FDM_P2P_ATTR                   Attributes of Promise to Pay; Required for
FDM_PERSONALIZE                Personalization of Collections Management
FDM1                           Cash Management & Forecast: Line Items of
FDM2                           Cash management line items from MM purchas
FDMV                           Cash Planning Line Items of Earmarked Fund
Hope this helps, award points if useful.

Similar Messages

Checklist for blueprinting phase in AR and Credit Management

Hi Guys! My company is in the blueprinting phase and they have assigned me as the blueprinting guy in the AR and Credit Management side. I would like to know if anyone has a checklist or can mention things about which i am supposed to look for and ask.
any help will be awarded with points. Thanks.

Hi Mahesh,
In order to change the horizon period in OVA8 you have to do it in transaction OMO1.
The consequences of this change are the following:
1. First of all, a reorganization of the credit values is necessary
so you have to run RVKRED77.
2. The change in the horizon will not affect already created orders
(it means that already created orders will not be blocked). This new
horizon will only affect newly created orders or "old" orders which are
changed and for which a new credit check is performed.
3. Date volume: when period= M, all orders for the same month and the
same customer create just one entry in S066 (you can check it through
SE16). However, when period= T, all orders for the same day and the
same customer create on entry in S066 (that means that nearly every
sales order gets an entry in S066).
Thanks and best regards,
Smile

Restriction of user to access dispute and Credit case as per organizational area

Hi Team,
Requirement is to restrict user to use dispute and credit case as per organizational area.
Company having different zones and business wants that the user of one zones should not access the dispute and credit case along with the attachement related to cases of another zone.
Now Company having one RMS ID for Dispute and One RMS ID for Credit case .
So need help to assist how should we proceed to restrict the user of different zones.
Thanks in advance .
Manoj

Hi Mark,
It is not company code . it is basically region by geographic like latin America, North America.
under oner region business have several company code.
Business want to restrict the user to use credit case and dispute case along with attachment limited by region.
Thanx,
Manoj

SAP Reports: Accounts Receivable and Credit Management

Good Afternoon Folks-
Can anyone give me a listing of all the AR and Credit Management Reports and what they tell?
I cannot find anything that tells me this report is good for DSO, etc.
Thanks!

Hi,
To View the Reports in Accounts Receivable , here is the menu path
Accounting - Financial Accounting - Customers - Information System - Reports for Accounts Receivable Accounting
Customer Balances
S_ALR_87012167 - Accounts Receivable Information System
S_ALR_87012172 - Customer Balances in Local Currency
S_ALR_87012186 - Customer Sales
S_ALR_87012169 - Transaction Figures: Account Balance
S_ALR_87012170 - Transaction Figures: Special Sales
S_ALR_87012171 - Transaction Figures: Sales
Customers: Items
S_ALR_87012168 - Due Date Analysis for Open Items
S_ALR_87012197 - List of Customer Line Items
S_ALR_87012173 - List of Customer Open Items for Printing
S_ALR_87012174 - List of Customer Open Items
S_ALR_87012175 - Open Items - Customer Due Date Forecast
S_ALR_87012176 - Customer Evaluation with OI Sorted List
S_ALR_87012177 - Customer Payment History
S_ALR_87012178 - Customer Open Item Analysis by Balance of Overdue Items
S_ALR_87012198 - List of Cleared Customer Items for Printing
S_ALR_87012199 - List Of Down Payments Open On Key Date - Customers
Master Data
S_ALR_87012179 - Customer List
S_ALR_87012180 - Address List
S_ALR_87012182 - Display Changes to Customers
S_ALR_87012183 - Display/Confirm Critical Customer Changes
S_ALR_87012195 - Customer Master Data Comparison
For Credit Management, the menu path is
Accounting - Financial Accounting - Customers - Credit Management - Credit management info system
F.31 - Overview
F.33 - Brief overview
F.32 - Missing data
FCV3 - Early warning list
FDK43 - Master data list
S_ALR_87012215 - Display changes to credit management
S_ALR_87012218 - Credit master sheet
This is for Ecc 5.0. to know more about the particular report, click on the program documentation (Shift + F1). The icon is in blue color and ' i ' is what u have to select to know more information about the report.
Hope it helps.
Regards
M.S.Reddy

What is the field and Table for "Batch Class" and "Class Type" in QM.

Hi All,
What is the field and Table for "Batch Class" and "Class Type" in QM.
Thanks,

Hi,
For batch class the class type value is '023' . This you can find from KLAH table and the fileld for class type is KLART..
And also all the data related to batch class are found in tables INOB, KLAH,KKSK and for the characeteristics of batch materials you can refer AUSP table.
In INOB table, for batch class, you need to give 023 in KLART field and value MCH1 in OBTAB filed.
Please check this and let me know if this you need any more details?

Start Of Ramp-Up for SAP Portfolio and Project Management 5.0

Start Of Ramp-Up for SAP Portfolio and Project Management 5.0
Starting with this new release, the application SAP Portfolio and Project Management 5.0
replaces both the SAP Resource and Portfolio Management (SAP RPM) application and the
Collaboration Projects (cProjects) application.
Start of ramp-up for SAP Portfolio and Project Management is 19th of April, 2010. The end
of ramp-up is currently scheduled for 19th of October, 2010.
Functional Innovations And New Features
A detailed description of all new and/or enhanced functional innovations and features can
be found in the Release Notes:
[http://service.sap.com/releasenotes |http://service.sap.com/releasenotes]
-> SAP Solutions
    -> Release Notes SAP Portfolio and Project Management
There are some SAP Notes which are in general very important for SAP Portfolio and Project
Management 5.0 and which also serve as central points of entry to find import information:
SAP Note [1377104|https://service.sap.com/sap/support/notes/1377104]      FAQs - SAP Portfolio and Project Management 5.0
SAP Note [1402912|https://service.sap.com/sap/support/notes/1402912]      PPM 5.0: Supported Browsers, Java versions, etc.
SAP Note [1411953|https://service.sap.com/sap/support/notes/1411953]      PPM 5.0: Configuration Content
SAP Note [1436778|https://service.sap.com/sap/support/notes/1436778]      SAP Portfolio and Project Management 5.0: Restrictions
Kind regards,
   Florian

Thanks very much for taking the time to post the info Florian. I will update this thread as well if I run into any new information.
Do we have any idea on SAP's direction for Product Definition? PD is still version 2.0 and I heard that PD functionality will be incorporated into PPM 5.0 which does make a lot of sense. I very briefly went through the notes and config doc in this post and did not get the impression that PPM has any idea and concept management capabilities.

Tables for Opportunity "Status" and "Reason"

Hi,
Can someone help me in finding the tables for determining "Status" and "Reason" for an opportunity along with the relvant text descriptions?
Regards,
Sandeep

Hi Sandeep,
Status- code in field stat of CRM_JEST table
                OBJNR = guid opportunity
                INACT = SPACE
        Text of status in TJ30T with your status profile
Reason- code in field code of CRMD_SRV_SUBJECT with
           guid_ref equal to guid_set( of crmd_link with objtype_set = 29 )
        Text of reason in QPCT
I hope this way help you.
Regards.
Manuel

Software for suspend/hibernate and power management?

After working with Arch on my desktop pc for a while, I today installed it on my laptop, as well. Everything works fine so far, but after reading through a lot of articles on the wiki and threads on this board, I'm a little confused about which tools I should use for hibernate/suspend and power management?
Cpufreq-utils, acpid, pm-utils, laptop-mode-tools, etc. What do you recommend for use?
Thanks in advance!
Last edited by mamr (2008-10-25 09:07:14)

All that you listed there have different functions. I use all the above on my laptop. Cpufreq-utils enables the frequency scaling, pm-utils (should) enables suspend and/or hibernate, laptop-mode-tools adds some power management functions, etc. Anyways, they're all useful for a laptop. Install, tweak, ask questions
Good luck!
Scott

Table for TDS sections and its description

Hi,
Is there any table where both TDS section and its description is getting stored? If this is possible can we relate the same to Vendor through any link?
Thanks & Regards,
Tapan

HI
J_1ITDSSEC is the table for TDS section and description.
TDS sections will be assigned to tax codes, so you can link through tax codes whatever is assigned to a vendor.
Relation will be -- Vendor-- Taxcode--tDS section.
Cheers
Mukta

Table for pricing komp and komk.

Hi gurus,
My requirement is i need to get a transparent table for 'Communication for Pricing Header' Structure is KOMK.
I need the table or view or through any function module by which we can get the pricing data.
I have values from table VBRP and VBRK.

Hi
Try the standard Fm " PRICING".
Tables for refernce : KONV and T683s.
Cheers
Ravish

What is the table for inbound delivery and PO

Hello,
I did one inbound delivery with reference to PO, the SD Documnet Category:7(Shipping Notification/Delivery)
I tried in LIKP,EKBE tables for Inbound delivery and PO relation.
I didnot find, Can i have the table name for findinh the PO and Inbound delivery in one table.
I want to fetch these two documents in to reports.
With regards
Lakki

I am sorry. I misunderstood your requirement. Please ignore my earlier post on this.
But do consider the below option :
You can get both Purchase Order as well as Inbound Delivery details in LIPS.
LIPS-VGBEL = Reference Document ( In this case it would be PO )
Hope this time it helps you.

Crm tables for sales group and sales office

Hello CRM Experts,
Can any one plz. help me to find Tables for Sales Group and Sales office.
It will be really helpful if the above fields have relation to the Business Partner.
Thanks in Advance,
Regards,
Bharat.

Hi Radek,
I feel the table which you have given is the right table but in my scenario we have created sales office and sales group(in org structure) independently in CRM, so now we need to find these values from the table independently as well as with relation to BP the table which you have provided can be used for second scenario but if we want to fetch the values of all sales office and sales group which table i have to use.
One more problem for second scenario is in BP we cant able to see the sales ofice & group values which we defined in CRM, if we can save BP with sales office and group values then only we can use the table which you have given
Highly appreciable for your replies.
Thanks,
Bharat.

Table entries for Personnel administration and organisation management

Hi ,
For a functional consultant do we need to remember the table entries where the employee infotypes saved or where the table entries is useful as far as Personnel administration and organisation management is concerned.....
and one more thing how to create a custom Infotype (employee) detail documentation required ...
keep me posted
Thanks

hi,
it is really helpful if you rember the table name which holds the information about the infotypes
table starting with PA contains all the personnel information data
like PA0001 holds the information of infoty0001
similary you can check for other info types
and hr haster table like HRP1000 or HRP1001 hold all the other hr objects including your personnel objects as well as organizational related objects
infotype numbers
Four digit number nnnn
Unique identification
9000 to 9999 reserved for customer infotypes
naming convention
0000 to 0999 HR Master data / Applicant data
1000 to 1999 Organizational Management
2000 to 2999 Time data
4000 to 4999 Applicant data
9000 to 9999 Customer defined
defination of infotypes
Each infotype nnnn requires at least two structures and one table:
Structure PSnnnn
 Structure PSnnnn contains all of the infotype data fields.
Structure Pnnnn
 Structure Pnnnn contains infotype key fields and all of the data fields
from structure PSnnnn .
Transparent table PAnnnn and/or transparent table PBnnnn
infotype module pool
A module pool should be used with each infotype. This module pool is the main program for the maintenance interface for the info type.
The name of the program is MPnnnn00. Where P stands for Human Resources (personnel) and nnnn is the four-digit info type number.
Transparent table PAnnnn is required if you want to use an infotype within Personnel Administration.
 If you want to use an infotype within Recruitment, transparent table PBnnnn is required.
In accordance with the distribution of infotype name ranges, objects P9nnn , PS9nnn , PA9nnn and PB9nnn are assigned to the customer name range.
infotype screen
An initial screen
A single screen
A list screen
Initial screen is used as technical interface
Screen 1000 is used for all info types
Processed in background and not displayed
Performs general initialization procedures
A single screen
Its an interface between the system and the user.
It enables to create, display or maintain data records.
Screen 2000 is used for single screen.
list screen
Unable to list all records in info type
Screen 3000 is used for list screen
infotype time constrains
A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:
A Only one record may exist, valid from 01/01/1800 to 12/31/9999. Splitting and deletion is not permissible.
B Only one record may exist, valid from 01/01/1800 to 12/31/9999. Splitting is not permissible, but may be deleted.
T The time constraint varies depending on the subtype.
Z Refers to time management infotypes.

to create infotype
Transaction code
PM01.
enhancing PA infotype
Start the Personnel Administration info type copier (PM01)
Enter the info type number.
Choose Enhance info type.
Start transaction PM01
You access the Create Info type screen:
Choose Enhance Info types.
In the Info type no. field, enter the four-digit number of the info type you want to create. When you specify the info type number, please remember to enter any leading zeros.
In the Sub-Objects group box, flag CI Include.
Choose Create. The Dictionary: Initial Screen is displayed.
Create the Cl include.
Choose Activate.
Return to the Create Info type screen.
Choose Create All.
hope this information will help you..
and don't forget to reward points

Tables for vendor invoice and payment

Hi Gurus.
I want to know from which tables i can get the information for folllowing points.
1. Vendor Invoices - Complete (Header and Item)
2. Vendor Payments Details Detail about payment method (check, wire, etc)
Please tell me tje table names.

There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
|Table Name |Table Description |
|/BEV3/CHKOMPAZVV |Append Structure CH -> CO PA |
|/CWM/ACCIT |Append Structure for Enhancement of Structure ACCIT in CWM |
|/CWM/KOMP |Catch Weight Management Enhancement |
|/DSD/TAXJURCD |Ship From Tax Jurisdiction Code: for Header Prc Comm Str |
|/SAPNEA/J_SC_LFA1 |Subcontractor Information |
|/SAPNEA/J_SC_LFB1 |Subcontracting Management |
|/SAPPSPRO/A_FI2_LONGNUM |IBU-PS: Append structure for structure NONBSEG |
|/SAPPSPRO/A_LONGNUMBER |additional fields for SPIIN number |
|/SAPPSPRO/EADD |Purchasing Document Header: Additional Data |
|/SAPPSPRO/EADD_DATA |Purchasing Document Header: Data Part Additional Information|
|/VSO/R_KNA1_A |Append to KNA1 for Vehicle Space Optimization |
|/VSO/R_KNA1_I |Additional Data for Vehicle Space Optimization for KNA1 |
|AACCHD_FMFG |US federal fields |
|AACCHD_PSO |IS-PS: ACCHD Append Structure for Payment Requests |
|AACCIT_GM |Append for Grants Management |
|AACCIT_PSO |IS-PS: ACCIT Append Structure for Payment Requests |
|AACCIT_SSP |Append for Payment Statistical Sampling Process |
|AACCIT_USFG |Append structure for US federal government |
|AAUSZ_CLR_USFG |Clearing information for US Fed (Tresury Confirmation) |
|ABKPF_PSO |IS-PS: BKPF Append Structure for Payment Requests |
|ABKPF_UMB |IS-PS: Append Structure for Transfer Transaction FMITPO |
|ABSID_PSO |IS-PS: Data appendix of open items customers |
|ABSIK_PSO |IS-PS: Data appendix of open items vendors |
|ABSIS_PSO |Local Authorities |
|ABUZ |Help Structure for Line Items to be Generated Automatically |
|ACCCR |Accounting Interface: Currency Information |
|ACCCR_FKEY |Key: Acctg Currency Data for Line Item Including Currency |
|ACCCR_KEY |Key: Accounting Currency Data for Line Item |
|ACCFI |Interface to Accounting: Financial Acctg One-Time Accts |
|ACCHD |Interface to Accounting: Header Information |
|ACCHD_KEY |Key: FI/CO Document Header |
|ACCIT |Accounting Interface: Item Information |
|ACCIT_EXTENSION |ACC Document: Additional Item Information |
|ACCIT_JV |Joint Venture Accounting |
|ACCIT_KEY |Key: FI/CO Line Item |
|ACCIT_WT |Withholding tax information for FI Interface |
|ACCRDF |Fields for Posting Small Differences: Preparation |
|ACC_DOCUMENT |Accounting document |
|ACC_KONTEXT |Context Info for FI Single Screen Transactions FB50 and FB60|
|ACERRLOG |Return Parameter |
|ACGL_HEAD |Fields for Document Header Entry Screen |
|ACGL_ITEM |Structure for Table Control: G/L Account Entry |
|ACSCR |Communication Structure for Field Modification SAPLFDCB |
|ACSPLT |Carrier for Split Information re: Current Account Line Items|
|ACSPLT_WTNEW |Proportion of New Withholding Tax |
|ACSPLT_WTOLD |Proportion of Old Withholding Tax |
|ADDR1_SEL |Address selection parameter |
|AEBPP_KNBK |Additional Fields Bank Data Biller Direct |
|AEBPP_LFBK |Additional Fields Bank Data Biller Direct |
|AFMIOI |Append for new fields ECC50/ERP |
|AFMIOI_USFG | SD order needs quantity |
|AFMISPS |Additional Fields for Table FMISPS |
|AFM_ACCIT_EXTENSION |Extension for FM Payment Update |
|AFM_FAGL_GLT0_ACCIT_EXT |Extension FM Account Assignments |
|AFM_FI_BKPF_SUBST |Append to Structure BKPF_SUBST |
|AFM_FMFCTF |Append for Fund Center substrings |
|AFM_FMFINCODE |Append for Fund substrings |
|AIFM01D |Append for IFM01D |
|AKNA1_FMFG |US Federal Government Customer Master Data Additional Fields|
|AKNA1_PSO |Local Authority Additional Fields |
|AKNB1_PSO |IS-PS: Customer Master Record, Additional Data (Co.Code) |
|AKNBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALFA1_FMFG |US Federal Government Vendor Master Data Additional Fields |
|ALFA1_PSO |Local Authority Additional Fields (Address) |
|ALFB1_FMFG |PS fields for company code-specific master data field |
|ALFB1_PSO |IS-PS: Data Appendix Vendor Master Record (Company Code) |
|ALFBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALVDYNP |ALV dialog screen fields |
|ALV_S_FCAT |Field Catalog (for LVC and for KKBLO) |
|ALV_S_FILT |Filter Criteria (for LVC and for KKBLO) |
|ALV_S_GRPL |Group Levels (for LVC and for KKBLO) |
|ALV_S_LAYO |Layout (for LVC and for KKBLO) |
|ALV_S_PCTL |Structure for Checking Print in ALV |
|ALV_S_PRNT |Print settings (for LVC and KKBLO) |
|ALV_S_QINF |Structure for Quickinfos of Exceptions |
|ALV_S_SGRP |Field Groups (for LVC and for KKBLO) |
|ALV_S_SORT |Sort Criteria (for LVC and for KKBLO) |
|ANBZ |Help structure for asset line item |
|ANLZACCOUNT |Additional Account Assignment Objects in Asset Accounting |
|ANLZACCOUNT_FKBER |Account Assignment Objects: ANLZACCOUNT with Function Added |
|ARC_PARAMS |ImageLink structure |
|AT003_XBLNR2 |Append structure for US federal government |
|AUSZ1 |Clearing Table 1 |
|AUSZ2 |Clearing Table 2 |
|AUSZ_CLR |Assign Clearing Item to Cleared Items |
|AUSZ_CLR_ASGMT |Assgt of Clrg Items - Cleared Items with Acct Assignment |
|AUSZ_INFO |Open item data for clearing transactions |
|AVBKPF_FMFG |US federal |
|AVBKPF_PSO |IS-PS: Append Structure VBKPF for Payment Requests |
|AVBSEGDPSO |IS-PS: Append Structure VBSEGD for Payment Requests |
|AVBSEGKPSO |IS-PS: Append Structure VBSEGK for Payment Requests |
|AVIK |Payment Advice Header |
|AVIP |Payment Advice Line Item |
|BALHDR |Application log: log header |
|BALMT |Application Log: Structure for a formatted message |
|BAL_S_CLBK |Application Log: Return routine definition |
|BAL_S_CONT |Application Log: Context |
|BAL_S_MSG |Application Log: Message Data |
|BAL_S_PAR |Application Log: Parameter Name and Value |
|BAL_S_PARM |Application log: Parameters |
|BAPIASCONT |Business Document Service: File Content ASCII |
|BAPIBDS01 |Business Document Service: Reference Structure for BAPIs |
|BAPICOMFIL |BDS: Command File for Transport Entries |
|BAPICOMPO2 |SBDS: Enhanced Component Information |
|BAPICOMPO3 |SBDS: Enhanced Component Information |
|BAPICOMPON |Business Document Service: Component Table |
|BAPICONNEC |BDS: Structure for BDS Links |
|BAPICONTEN |Business Document Service: File Content |
|BAPIDPROPT |BDS: Structure for Properties |
|BAPIFILES |Business Document Services: Transfer Table for File Names |
|BAPIPROPER |BDS: Structure for Properties |
|BAPIPROPTL |BDS: Structure for KPRO Properties |
|BAPIQUERY |BDS Structure for Query Table |
|BAPIRELAT |Business Document Service: Relations |
|BAPIRET1 |Return Parameter |
|BAPIRETURN |Return Parameter |
|BAPISIGNAT |Business Document Service: Signature Table |
|BAPISRELAT |Business Document Service: Relationship Table with Signature|
|BAPIURI |Business Document Service: URI Table |
|BDCMSGCOLL |Collecting messages in the SAP System |
|BDCRUN |Batch input: Runtime analysis |
|BDIDOCSTAT |ALE IDoc status (subset of all IDoc status fields) |
|BDI_SER |Serialization objects for one/several IDocs |
|BDN_FKT |Business Document Navigator: Functions to be Excluded |
|BDWFAP_PAR |Parameters for application function module - IDoc inbound |
|BDWFRETVAR |Assignment of IDoc or document no. to method parameter |
|BDWF_PARAM |Parameters for workflow methods for IDoc inbound processing |
|BKDF |Document Header Supplement for Recurring Entry |
|BKDF_SUBST |Process Interfaces: Substitutable fields during posting |
|BKORM |Accounting Correspondence Requests |
|BKP1 |Document Header Supplement for Update |
|BKPF |Accounting Document Header |
|BKPFBU_ALV |Document Overview: Display Document Headers in ALV Grid Ctrl|
|BKPF_CARD |Credit Card: Append for BKPF |
|BKPF_LINE |Item Category for XBKPF_TAB |
|BKPF_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BKPF_USFED |Append structure for US federal government |
|BLNTAB |Document Number Table for Financial Accounting |
|BNKA |Bank master record |
|BNKAAPP |Appendix to Table BNKA |
|BNKT |Conversion of temporary to internal bank keys |
|BOOLE |Boolean variable |
|BSEC |One-Time Account Data Document Segment |
|BSEC_LINE |Item Category for XBSEC_TAB |
|BSED |Bill of Exchange Fields Document Segment |
|BSEE |Changeable Fields in the Line Item |
|BSEG |Accounting Document Segment |
|BSEGL |Document Segment: Fields Derived for Line Layout Variant |
|BSEGS |G/L Item Transfer Structure for Single Screen Transactions |
|BSEGT |Transfer Table for the Tax Postings to be Generated |
|BSEGZ |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
|BSEG_ALV |Document Overview: Document Item Display in ALV Grid Control|
|BSEG_LINE |Item Category for XBSEG_TAB |
|BSEG_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BSET |Tax Data Document Segment |
|BSEU |Line Item Additional Information (Update) |
|BSEZ |Line Item Additional Information (Online) |
|BSEZ_LINE |Line Item Category for XBSEZ_TAB |
|BSID |Accounting: Secondary Index for Customers |
|BSIK |Accounting: Secondary Index for Vendors |
|BSIP |Index for Vendor Validation of Double Documents |
|BSIS |Accounting: Secondary Index for G/L Accounts |
|BSIX |Index table for customer bills of exchange used |
|BTXKDF |Fields for Exch.Rate Difference Posting for Taxes |
|BVOR |Intercompany posting procedures |
|CACS_A_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_A_CUST_COND |Commissions: Customer Fields Condition Technique |
|CACS_A_FIELDSPRICING |Append for Condition Technique Fields from Commission System|
|CACS_S_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_S_CUST_COND |Condition Attributes |
|CACS_S_FIELDSPRICING |Comm.: All Condition Technique-Relevant Commission Fields |
|CACS_S_FSINS |Customer Fields for Condition Technique of Insurances |
|CCDATA |Payment cards: Database fields relevant to both SD and FI |
|CFW_LINK |CFW: Link Info of a Container |
|CI_COBL |Extension |
|CKI_ACCIT_ML |Transfer from MM to ML in accit-structure |
|CNTLSTRLIS |Control stream list |
|COBK |CO Object: Document Header |
|COBK_ONLY |Non-key fields only in COBK (INCLUDE structure) |
|COBL |Coding Block |
|COBLF |Coding block: Tax table structure |
|COBL_COKZ |Assignment types for CO account assignments |
|COBL_DB_INCLUDE |Include with Additional Account Assignments for DB Tables |
|COBL_EX |Coding Block for External Applications (Not CO/FI) |
|COBL_FI |Fields from COBL that Must not Be Overwritten in FI |
|COBL_FM |Additional Fields for FM |
|D010SINF |Generated Table for View D010SINF |
|D020S |System table D020S (screen sources) |
|D020T |Screen Short Description |
|DBSEG |Dialog Supplementation BSEG (Taxes) |
|DD02L |SAP Tables |
|DD03P |Structure |
|DD03V |Table fields view |
|DD07V |Generated Table for View DD07V |
|DD23L |Matchcode ID |
|DD32P |Interface structure for search help parameters |
|DDSHDEFLT |Description of a default value for search help fields |
|DDSHDESCR |Interface: elementary search helps of a search help |
|DDSHFPROP |Characteristics of search help parameters |
|DDSHIFACE |Interface description of a F4 help method |
|DDSHRETVAL |Interface Structure Search Help <-> Help System |
|DDSHSELOPT |Selection options for value selection with search help |
|DDSUX030L |Nametab Header, Database Structure DDNTT |
|DDSUX031L |Nametab Structure, Database Structure DDNTF |
|DDTYPES |Table of all Dictionary types and classes |
|DFIES |DD Interface: Table Fields for DDIF_FIELDINFO_GET |
|DISVARIANT |Layout (External Use) |
|DOKHL |Documentation: Headers |
|DPPROPS |General property structure for data provider |
|DTC_S_LAYO |Structure for Design of Double Table Control |
|DTC_S_TC |Structure for table controls in the double table dialog box |
|DTC_S_TS |Tab Title Structure |
|DYNPREAD |Fields of the current screen (with values) |
|E071 |Change & Transport System: Object Entries of Requests/Tasks |
|E071K |Change & Transport System: Key Entries of Requests/Tasks |
|EAPS_20 |Field Enhancements for EA-PS 2.0 |
|EDIDC |Control record (IDoc) |
|EDIDS |Status Record (IDoc) |
|EDIFCT |IDoc: Assignment of FM to log. message and IDoc type |
|EDIMESSAGE |Transfer Structure with all Sy Fields for T100 |
|EDI_DS |Status record for interface to EDI subsystem |
|EDI_HELP |Help Structure for Reference Fields in EDI Function Groups |
|EK05A |Communication Area Purchasing - Financial Accounting |
|ESKN |Account Assignment in Service Package |
|EUDB |Development Environment Objects |
|EUOBJ |Workbench: Development Objects |
|EXCLTAB_LINE |Lines of EXCLTAB with OK Code to be Deactivated |
|EXISTING_DOC |Original Document |
|F05ACTRL |Control Fields for SAPMF05A and Subprograms |
|FAGLBSEGL_S |Additional Sender Flds from General Ledger for Doc. Overview|
|FAGL_GLT0_ACCIT_EXT |Line Information for Document Splitting |
|FAGL_MIG_S_BUKRS_LEDGER |Combination of Company Code and Assigned Ledgers |
|FAGL_SPLIT_FLD_S |Characteristics Permitted for Split |
|FAGL_S_APPLICATION |Application and Subapplication |
|FAGL_S_BALDIM |G/L Characteristics of Document Split in New General Ledger |
|FAGL_S_BUKRS |Structure with Company Code |
|FAGL_S_BUKRS_EXT |Structure: Company Codes --> Ledgers |
|FAGL_S_CURTYPES |Currency Types of a Ledger |
|FAGL_S_MIG_001 |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S |
|FAGL_S_MIG_MGPLN_EXT |Structure: Extended Migration Plan Information |
|FAGL_S_T8G40_BS |Split Fields with Characteristic "Balance Sheet" |
|FCRD_VBKPF |Credit Card: Include for Appends for BKPF, VBKPF |
|FCRD_VBSEG |Include for Appends for VBSE* |
|FDM_AR_CASE_ATTR_1 |FSCM DM: |
|FDM_AR_LINE_ITEM |FSCM: DM |
|FDM_AR_RFPOS |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
|FELD |Screen Painter fields (internal) |
|FICCO |Adjustment Values for External Document Items |
|FICCT |Totals Information for Interclient Posting |
|FICTX |Tax Information for ICT |
|FIELDINFO |Field attributes for a specific field |
|FIN1_PARAM |OBNG: Trans. structure for official doc. numbering (global) |
|FIN1_PARAM_FI |OBNG: FI parameters |
|FIN1_PARAM_MM |OBNG: MM Parameters |
|FIPEX_STRUC |Subfields Commitment Item |
|FIPOEXT |Help structure for line items to be generated automatically |
|FIREVDOC |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS |
|FISTL_STRUC |Substructure Fund Center |
|FM01 |Financial Management Areas |
|FMBLSTRING_COMPONENTS |Component of the BL String |
|FMCI |Commitment items master data |
|FMDY |FIFM: Screen Fields |
|FMFCTR |Funds Center Master Record |
|FMFG_ACCIT_EXTENSION |Extention for all fields that have to be transfered into BL |
|FMFINCODE |FIFM: Financing code |
|FMFPO |FIFM: Commitment Item |
|FMHRBA_NEG_DOC_TYPES |HR Integration: Doc. Types for Negative Funds Commitments |
|FMHRBA_SETTINGS |Integration with HR: Settings |
|FMHRBA_VAD_SETTINGS |HR Integration: Generate Value Adjustment Docs for Changes |
|FMICCN |FM: Append Structure for FMIOI (CCN Fields) |
|FMIDATA |Common Data for Funds Management Actual Data |
|FMIDATAFI |Clean FI Data for Funds Management Actual Data |
|FMIDATAOI |Clean Open Item Data for Funds Management Actual Data |
|FMIFIIT |FI Line Item Table in Funds Management |
|FMIKEY |Common Key for Funds Management Actual Data |
|FMIKEYFI |FI - Key for Funds Management Actual Data |
|FMIKEYOI |Common Key for Funds Management Actual Data |
|FMIOI |Commitment Documents Funds Management |
|FMIOIKEY |Key for Table FMIOI |
|FMIOI_USFG | SD order needs quantity |
|FMIREF |Ref. Funds Management Actual Data to Preceding Document |
|FMISPS |General Parameters for Funds Management |
|FMIT |Totals Table for Funds Management |
|FMMRESERV |Include for the Reduction of Funds Reservations (FM) |
|FMRFC |Function Modules and their RFC Destinations |
|FMSP_SPLIT_FIELDS |PSM Fields used in multiple account splitting |
|FMT001 |Additional Customizing for Funds Management |
|FMUP00T |Update Profiles |
|FMUP01 |Update Control with Value Type Dependency |
|FMUP_INV_KEY |Extension for FM Update: FI Key of Invoice |
|FMUP_PAY_KEY |Extension for FM Update: FI Key of Payment |
|FS006 |Fields for Optical Archiving |
|FTCHECK |Foreign Trade: Import Simulation - Ctrl Fields for Pricing |
|FTEXTS |Communication Structure for Additional Components |
|FTGENERAL |Foreign Trade: General Fields Item |
|FUND_STRUC |Substructure Fonds |
|FVD_TZB0A |Append to TZBOA: Loans Fields |
|GLACCOUNT_CCODE |G/L Account Master Record: Company Code |
|GLACCOUNT_CCODE_DATA |G/L Account Master Record: Company Code - Data |
|GLACCOUNT_CCODE_INFO |G/L Account Master Record: Company Code - Information |
|GLACCOUNT_CCODE_KEY |G/L Account Master Record: Company Code - Key |
|GLX_ORG_INFO |Organizational Assignment |
|GMBSEGZ |Grants Management Add-on |
|GXXLT_H |XXL interface: horizontal features |
|GXXLT_O |XXL_interface: texts for online display |
|GXXLT_S |XXL interface: structure of the semantics table |
|GXXLT_V |XXL interface: vertical features |
|HELPVAL |Restrict Value Range - Transfer Table |
|HELP_INFO |Transfer Values for the Help Processor |
|HELP_VALUE |Structure or Function Module HELP_VALUE_GET_FOR_TABLE |
|HHM_COBL |Include for COBL from FM |
|IADDR_PSO |Local Authority Additional Fields (Address) |
|IBKPF_PSO |IS-PS: Include Structure BKPF Payment Request Doc.Header |
|ICDIND |Structures for generating change document update programs |
|ICON |Icons table |
|ICONS |Icons |
|ICURR |Interface for Currency Translation

Letter of Credit functionality and Credit Management

Hi,
we want to use Letter of Credit functionality for exports.
Currently, we have an ERP system that contains the sales data. In a separate system we have the credit management functionality (Financial Supply Chain Mgt - FSCM).
When order is created, the credit limit is checked in the FSCM system (via PI messages).
Now, we want to link some of the Sales orders with Letter of Credit. I believe, this is standard functionality in GTS.
So when Sales Order is created a LOC should be connected to this.
Can the GTS be connected also to FSCM credit management, so credit limit is not affected?
Example:
Sales Order value: 1 Mio USD
10% down-payment > this would be in the credit exposure visible (net exposure).
90 % covered through LOC > credit exposure should showing this, or it shows order value and in a negative figure this amount deducted so no effect on exposure.
Down-payment has no relation to LOC. When money is received for this the net exposure of the sales order is 0.
partial invoice: 0.4 Mio USD > it should be possible to link this invoice to the LOC. The posting FI document should have some LOC information, so when payment comes in the amount in LOC is reduced as well as in credit management this open.
Final invoice 0.5 USD: as above, all values go out from exposure if there are any.
A second case would be guarantees, where there is no reduction of values. This would stay same.
Anyone who can advise a solution here?
Thanks + Regards
Hein

Letter Of Credit can be used as a standard solution of SAP GTS with ERP solution. Yes you can connect both SAP & no SAP systems with GTS, but plugins, PI etc needs to be built in. But it would not be real time like RFC works. There are some standard available which needs to be hard coded to meet specific requirements.
Connecting LOC to Sales Order, invoice etc, is manual, based on business specific parameters and it comes standard with SAP GTS. Maintaining Values & Quantity of LOC based on actual LOC from bank is also possible. The depreciation of values & quantities is also standard with in LOC in GTS.
You can also setup various communication methods for LOC.
I think when Invoice is raised and payment is received the LOC should be closed in the system. There can also be other scenarios where in system determines LOC based on predefined logics for determination strategy put in to the GTS system.
Cheers,
Abir

Tables for Collection, dispute and credit management

Similar Messages

Maybe you are looking for