Morethan 999 line items for vendor invoices
Hi All,
we had issue for an Invoice upload.
we are uploading the Invoice contains morethan 999 line items. but we are facing error for morethn 999 line items can't post when uploading thorugh ZFB60 transaction.
please advise if any SAP notes are exist or any idea.
Thanks and regards
Prathap
< Please search. >
Hi,
What error you are getting? Can you tell me clearly....
Regards,
Mohan.
Similar Messages
-
How to upload morethan 999 line items for a document?
if we need to upload more than 999 lines for a header.
How can we do that?hi,
you have to post like that
line P-key account value
Document 1001
898 40 123456 100
899 40 234567 200
900 50 333333 300-
Document 1002
001 40 333333 300
002 50 345678 250-
003 50 789654 50-
acc. 333333 is a interim account(in german: Zwischenkonto)
Message was edited by: Andreas Mann -
Separate line item for each invoice in payment document
Dear Experts,
while making payment for a vendor through F-58 for multiple invoices, the system grouping the invoices on Business Area basis and giving the line items.
For example there are 2 invoices for 5000 and 6000 in one BA and another 2 for 4000 and 9000 in second BA, the system is generating the entry as follows
Vendor A/c Dr BA1 11000
Vendor A/c Dr BA2 13000
Bank A/c Cr 24000
I want the system to generate separate line item for each invoice instead of 2. How do i do it?
But this is not happening when i am making partial payment and in that case it is generating 4 line items.
regards
SureshThanks for the reply
Checked it but still it is working in the same way.
It is a requirement for the client, is there anyway to do it?
Regards
Suresh -
More than 999 line items for an FI Document
Hello All,
Per SAP standard, an accounting document can only contain up to 999 line items. However, we have Logistics posting (Backflush) that would yield more than 999 line items in FI. We can't opt for setting summarization in transaction OBCY (FI Summarization based on Object Type) since this would affect GR/IR clearing. We can select reference transaction key MKPF (Material Doc Table) and table BSEG (Field MENGE <Qty>) but GR/IR clearing would be affected since definition of clearing is at Purchasing Doc (EBELN) and Item (EBELP).
Do you have other recommendations?
Thanks.Dear scorpio0485,
Yes ! I have already done posting for morethan 999 line items. but in the standard program we cant do it. We need to go for Z process.
In Zprocess we need to put one cut off line item for ex : 900 or 950. After that hardcode one GL code(clearing GL Code) in program to split the line items. Means the system generates 2 documents.
Please give the following Code to ABAPer
AT END OF xblnr.
mtab[] = ttab[].
CLEAR v_count1.
DESCRIBE TABLE ttab LINES v_lines.
LOOP AT ttab INTO wa_ttab.
v_tabix = sy-tabix.
v_count = v_count + 1.
IF v_count EQ 900.
count = count + 1.
v_count1 = v_count + v_count1.
MOVE-CORRESPONDING wa_ttab TO wa_xtab.
IF v_wtotal < 0.
wa_xtab-newbs = '40'.
wa_xtab-newko = '00003100001'.
ELSE.
wa_xtab-newbs = '50'.
wa_xtab-newko = '00003100001'.
ENDIF.
IF v_dtotal < 0.
wa_xtab-newbs = '40'.
wa_xtab-newko = '0003100001'.
ELSE.
wa_xtab-newbs = '50'.
wa_xtab-newko = '0003100001'.
ENDIF.
IF v_dtotal LE 0.
v_dtotal = v_dtotal * -1.
ENDIF.
IF v_wtotal LE 0.
v_wtotal = v_wtotal * -1.
ENDIF.
wa_xtab-prctr = '0000900008'.
wa_xtab-dmbtr = v_dtotal .
wa_xtab-wrbtr = v_wtotal .
If you need anymore,please let us know -
Why two line items for vendor credt
hi EXperts,
At the time of doing MIRO entry , System has generated two line items for vendor credit
GI/IR dr 2275.00
Vendor cr 2252.25
Vendor cr 22.75
That means while 1% of the INvoice value system has created one more line item.
Pls suggest why it has created like this. don't offer points
Thanks in Advance,
Arabinda Paridado you have a split payment term (different due dates) as defined in OBB9
-
Withholding Tax line item in Vendor Invoice (F-43)
I am implementing EXT Withholding Tax for a client. I have made all the settings but while doing the invoice after selecting the withholding tax codes for the vendor, system is not showing any line items for the withholding tax.
I have made the settings like this:
Defined business place, section codes, withholding tax keys, tax types, tax codes, applied the tax codes in the vendor master with 'liable' tick, defined in the tax code the posting indicator 1 for posting separate line item and activated the Ex Withholding tax in the company code. I have also made the field status of withholding tax as optional for posting key as well as FSV for GL accounts involved in the postings. Also made the vendor account group field status as optional for Withholding tax postings.
I am not getting where I have missed. System is also not shooting any error.
Please share your views.Hi,
Did you do Configuration steps of Extended Withholding Tax(EWT) as follows.
1.Define withholding tax type for invoice posting
IMG----->financial accounting>financial accounting global settings>withholding tax---->
Extended withholding tax-->calculation>withholding tax type--
>define withholding tax
type for invoice posting
2.Define withholding tax type for advance posting
IMG----->financial accounting>financial accounting global settings>withholding tax---->
Extended withholding tax-->calculation>withholding tax type--
>define withholding tax
type for payment posting
3.Define withholding tax codes
IMG----->financial accounting>financial accounting global settings>withholding tax---->
Extended withholding tax-->calculation>withholding tax codes--
>define withholding tax
codes
4.Define formulas for calculating withholding tax
IMG----->financial accounting>financial accounting global settings>withholding tax---->
Extended withholding tax-->calculation>withholding tax codes--
>define formulas for calculating withholding tax
5.Assign Withholding tax type to company code
IMG-->Financial accounting--->financial accounting global settings>withholding tax----->
extended withholding tax-->company code--
>assign Withholding tax type to company code
6.Activate extended withholding tax
IMG-->Financial accounting--->financial accounting global settings>withholding tax----->
extended withholding tax-->company code--
>activate extended withholding tax
7.Assignment of accounts for automatic posting-----OBWW
IMG---->financial accounting--->financial accounting global settings>withholding tax--->extended withholding tax>postings>accounts for withholding tax--
>define accounts for withholding tax to be paid over
8.Maintain company code settings for india
IMG----->logistics-general--->tax on goods movements>India>basic settings--
> maintain company code settings for india.
9.Assign tax codes in vendor master----
XK02
Regards
Venkat -
Hi experts,
I have one validation its like suppose if u have 999 line items then that record should b closed and the both +ve, -ve values should be equal to 0 n new record should start again.
if any body can help me in this regard then i will b thankful to them.
Regards
BohraBecause there may be automatic entries created, you shouldn't go to 999 entries. It should be OK to use 950.
Let's say you have 1100 entries. the first 950 total 10,000 credit. You create the first transaction with 950 entries and then an entry to a control account for 10,000 debit. Then another transaction with the remaining 150 entries and an entry to the same control account for 10,000 credit.
Rob -
Debit line item in vendor account
Hi,
How to manage debit line items in vendor in fbzp (F110)?Hi,
FBZP is a transaction to maintain payment methods for country, company codes and give a banking information for the comapny code. U can also specify the ranking of bank accounts and payment methods u wanna use for payment in APP(F110).
Vendor line item appears wen u make a payment by ur bank account by manual or APP.
So vendor debit line item will directly come from the setting of bank accounts u do in FBZP.
The bank account which gets credited while APP becomes the debit line item for vendor.
thanx
alok -
More than 999 line items in Invoice
Hi All,
We are having a scenario where more than 999 line items needs to be invoiced in a single billing document. If more than 999 line items are invocied in a single billing document, system can not post the acct document. Our requirement is to create single billing doc for more than 999 and post acct document also successfully.
Please advise if any one has worked on the simillar issue.
Thanks,
RaviHi,
You can not do that with 999 line items in one billing document, the reason is the line items limit in the accounting document, because one line item of billing document must generate two line items (D&C) in the accounting document, although you can maintain the max 999 line items in billing document, but actually the max line items of billing document is 499.
So the other line items more 499 must be generate in a new billing document! Hope can help you understand the scenario.
Regards
Tao -
Need some help on workaround for more than 999 line items in a FI document
Hi all,
user would like to know if there is any way to increase the maximum # of lines for an FI document. Currently, as SAP only allows 999 lines per FI document. The user is encountering an issue when a taxable invoice is uploaded because SAP creates additonal lines for the taxes thereby increasing the line item count beyond the 999 limit. This causes the user to separate out the upload files into several different files which is very time consuming. i have read some replies from previous questions posted on this but none were clear enough on how to actually split the lines and what will happen after the split to the rest of the line items how is the continuation with the first document. can some one give me the explanation or steps on how we can do the split on this document please. we are on 4.6c version. if we have to write some code, what should i explain to the abaper? any kind of inputs would be greatly appreciable.
Thanks in Advance
JayHi,
From your comments, I understand that you are uploading the journals. The steps to handle 999 line items limitation is through functional and technical help.
1. create a dummy GL account
2. In the code, ask the abaper to have a logic such that if more than 900 lineitems (dont check for 999, as some auto postings will be done), then the balance should be loaded to the dummy GL account created and a document should be posted
3. Start reading the remaining docs and follow the same logic as in 2 and ensure that the posting happened in step 2 against dummy GL account should have reversal posting. That is, if step 2 dummy GL account has a credit balance then in step 3 against the same amount a debit entry for the GL account should be posted.
This will ensure that once all the line items are posted, the balance in dummy GL is Zero.
Regards,
Sridevi -
+ 999 line items invoice posting in MM
Hi,
How can you manage +999 line items invoices in MM?
Now those invoices are treated in FI, using a program developed that allows the system to split the document in smaller ones, but in the future we want to post them using MM.
There is someone who find a solution to that? Which are best practice in this topic?
thks!
Edited by: Csaba Szommer on Jan 14, 2012 6:19 PMThe invoice was successfully posted. I have done 2 thing:
1) I got implemented User Exit: EXIT_SAPLMRMH_011 in Enhancement: MRMH0002
2) Maintained Transaction VS5 and G/L account no. for relevent chart of accounts in R/3 table T030K. -
How to limit line items for 999
Hi Gurus
i heard that a standard setting should be there to all company codes to create a second accounting document as soon as the number of lines reaches 800 or above lines. Can you tell me where to check this settings ?
can you tell me the check on number of lines in the accounting document that is being generated.
kind regards
SunithaHi Sunitha,
As far as my knowledge goes, there is no specific configuration from FI side where you tell the system the maximum line items to be posted in a FI document. The limit of 999 is inbuilt in SAP programs. You have some options to summarise the line items in configuration.
SAP has given various notes on summarisation as well as problems we encounter when we post a document with more than 999 line items. In my experience, I have seen a second document being posted automatically when you have more line items with the 1st document containing 991 lines and where the second one has the rest of the lines.
Thanks
Aravind -
Hi all,
In the SD, for One Post Goods Issue Material document and FI document generated.
Accounting document contains two line items.
If the Post Goods Issue contains More than 500items then in FI document generates with more than 1000 line items.
But as per std SAP, Per document 999 line items only.
Client wants to post at a time more than 500 items (DN) Post Goods Issue then more than 1000 line items generated.
How to post morethan 500 items in DN.
Thanks
venuHi
OSS Note 36353:
Summary
Symptom
When you post documents using the AC interface (from SD, MM or other applications), items appear in the FI document which are identical in all or in almost all fields.
This can also cause error message F5 727 ("Maximum number of items in FI reached"). The system issues this error if more than 999 items occur in an FI document.
Other terms
SAPLFACI, VF01, VF02, VF04, MB01, MB11, MR1M, CO15, BSEG, totaling,
document summarization, CKMI_RUN, F5 272, F1 807
Reason and Prerequisites
The system will only total items in the FI document if you made the proper settings for this action in Customizing (= sending application, for example: VBRK for SD, MKPF for MM Position Management, RMRP for MM Logistics Invoice Verification).
There is no summarization, for documents which are entered in FI (object type BKPF) application (for example EDI invoice receipt, FB01, MR0) or in invoice verification (MR01) (with object type BKPF).
The system can only total items in the FI document if they have the same account assignments and only differ in the value fields.
It is therefore not possible to carry out the totaling across different G/L accounts.
The summarization can be achieved by deleting certain fields in all items (can be configured in Customizing).
As a consequence, these fields will not contain data in the FI document. They are therefore no longer available for selection, clearing or reconciliation with other applications.
This field deletion only affects the FI document, not documents from other AC applications.
The field contents deleted in the FI document are still available for the other AC applications and can be updated there. The AC applications are not updated on the basis of the FI document. In addition, there are other summarization procedures in other applications, for example in CO (Note 147766).
Solution
Procedure for configuring summarization:
Carry out the following actions for each object type (sending application, AWTYP field), for which you want to summarize FI documents.
You can find the AWTYP object type on the detail screen 'Document header' under the 'Name' field when you display the document using transaction FB03.
1. If you think an FI document has too many items, find out in which fields the items differentiate.
To do so, display the FI document (FB03) or table BSEG and ONE FI document (SE16).
2. If there are items which are the same in all same account assignments:
Make the following entry in the TTYPV table (transaction OBCY):
Table Field name
As a consequence, items which are the same in all fields except value fields are totaled, that is, they are combined into a single item.
(The '* ' entry can only be made in Release 3.0D or higher.) If you use a release lower than 3.0D, enter any field which, when deleted, will not disrupt transactions from the affected application. As of Release 4.0, the ' ' entry can no longer use transaction SM31 (view maintenance) to make the entry in the TTYPV table. Check whether you can replace the entry ' ' with a field name. The corrections from this note enable you to use the report ZTTYPV to enter ' *' for the relevant object type.)
3. If there are ITEMS which differ in specific fields:
Enter the fields in the TTYPV table.
The contents of the fields entered in the TTYPV table are deleted.
This has a higher summarization effect than entry '* *'!
Typical fields for each application are:
Application AWTYP Table Field name
SD VBRK BSEG MATNR
Billing MEINS
MENGE
PAOBJNR
POSN2
VBEL2
WERKS
MM MKPF BSEG BPMNG
Position Management BPRME
ERFME
ERFMG
MATNR
MEINS
MENGE
PAOBJNR
POSN2
WERKS
BWTAR
MM RMRP BSEG BPMNG
Logistics BPRME
Invoice Verification ERFME
ERFMG
MATNR
MEINS
MENGE
PAOBJNR
WERKS
As of 4.0A
HR HRPAY see Note 116523
Payroll accounting
The list of the allowed fields in Release 3.1I includes the following entries in the TTYPS table:
BSEG BPMNG
BSEG BPRME
BSEG BWTAR
BSEG ERFME
BSEG ERFMG
BSEG MATNR
BSEG MEINS
BSEG MENGE
BSEG PAOBJNR
BSEG POSN2
BSEG PPRCT
BSEG VBEL2
BSEG WERKS
BSEG PRCTR (for restrictions see below)
BSEG FKBER (Note 413418)
General remarks:
Items with identical account assignments but different debit/credit codes (BSEG-SHKZG) will NOT be put together as a single item (for example, revenues and sales deductions in billing documents).
In releases lower than 3.0F, the system did not allow all of these fields as entries for the TTYPV table. To expand the number of fields allowed for the TTYPV table, enter the fields in the TTYPS table. (Call transaction SM31 (view maintenance) to add an entry to the V_TTYPS view.) (You can only add the BSEG BWTAR field using transaction SE16 (table maintenance) for the TTYPS table). The standard system only contains the BSEG-PRCTR field is only contained in the TTYPS table as of Release 4.6B.
This is an SAP table modification. Only enter the fields listed above. Do not enter any other fields without first contacting SAP, since these fields will then be deleted in every FI document from the application in question.
Notes:
When you carry out summarization using the material number (MATNR) during position management or invoice verification transactions, the 'material number' information is lost in the BSEG document table of Financial Accounting. Therefore no entries are written to the BSIM table. This can have the following consequences:
Transactions such as MR51 (accounting documents for material) or MB5B (balance at posting date) produce incorrect results.
The evaluation of balances at material number level (characteristic 0MATERIAL) in the SAP Business Information Warehouse displays faulty or incomplete results.
You can no longer use the Value Flow Monitor (transaction CKMVFM) to compare differences at material level between price difference accounts and the relevant FI postings.
If you delete the material number (MATNR), the amount (MENGE), the unit of measure (MEINS) or the plant (WERKS) in position management, this information is no longer available in financial accounting. The RMVKON00 report (transactions MRKO and MRPI) however, which indicates and settles the consignation stock, is based on the documents of financial accounting. This has two consequences:
If the FI documents are not summarized, each individual withdrawal is indicated in the report and can also be individually settled. If the FI documents are summarized, several withdrawals can be displayed in one single report line and can no longer be separately settled. Furthermore, certain data, such as material number, amount and unit of measure, may no longer be displayed.
If in the FI documents the material number or the plant is deleted and you settle the withdrawal, the tax codes that you defined using the tax indicator (in the material master) or in a purchasing info record can no longer be found. Instead, only the tax code that you defined as default value in the Customizing settings for the invoice verification (transaction OMR2) is determined. If no valid tax code has been defined there, the settlement terminates with message FF 704.
Read Note 38982 to learn how to determine the tax code.
In Release 4. 0A, these restrictions no longer apply to the RMVKON00 report.
Clearing of the GR/IR clearing account for each purchase order item: The account assignments to the purchase order (EBELN) and to the purchase order item (EBELP) are NOT deleted by default. In both the goods receipt with reference to the purchase order (MB01) and the invoice verification, they are assigned to an account in the FI document and thus PREVENT the summarization of the FI document.
This makes it possible to clear the GR/IR clearing account at purchase order item level.
Using Profit center for summarization
If you summarize using the Profit center field in FI, only FI and PCA balances can be reconciled at account level.
A summarization using the Profit center field is only worthwhile if other CO account assignments are also summarized. These account assignments are therefore also not available for a derivation of the Profit center field when the FI document are subsequently posted to Profit Center Accounting using transaction 1KE8. Since summarized documents are always postings the original of which is not posted in FI, you should subsequently post such documents from the sending application component anyway. However, you can directly transfer unoriginal FI documents using Note 102634 or, as of Release 4.5B, using the standard system. In this case, you must make sure that this function is not used for the summarized documents.
For the reason stated above, a summarization using the Profit center field is only worthwhile for transaction HRPAY. Note that HR only supports a subsequent posting from the sending application component as of Release 4.5A. In the releases 4.0A up to and including 4.0B, no programs are available in the standard system to generate subsequently the profit center document. You should implement Note 118533 in these releases beforehand to make sure that the online document flow from HR to PCA works.
A summarization using the Profit center field should definitely not be carried out in Releases 4.0A and 4.0B if the online update to Profit Center Accounting has not been activated in the fiscal year or if it should be activated subsequently (mid-year).
Header Data
Release Status: Released for Customer
Released on: 11.10.2007 08:21:39
Priority: Correction with medium priority
Category: Customizing
Primary Component: FI Financial Accounting
Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_APPL 30 300 31H
SAP_APPL 40 40A 40A
SAP_APPL 45 45A 45A
SAP_APPL 46 46A 46A
SAP_APPL 470 470 470
SAP_APPL 500 500 500
SAP_APPL 600 600 600
Highest Implemented Support Package
Support
Packages Release Package
Name
SAP_APPL 40B SAPKH40B28
SAP_APPL 45B SAPKH45B09
SAP_APPL 46B SAPKH46B01
SAP_HR 40B SAPKE40B28
Related Notes -
How to clear vendor open items if vendor invoice currency and payment currency different
Hi All.
How to clear vendor open items through f-44 if vendor invoice currency is EUR , payment currency is USD but local currency is INR
while clearing through f-44 system showing error as "to large for clearing clearing is not possible"
I checked all configuration, configuration wise no problem
BR.
ChandraHi Chandra,
You chose any one of the currency i.e. EUR/INR/USD for clearing in F-44. After selecting line items for clearing, system will show a difference. Click on over view button and manually write off the difference by selecting any one account i.e. dummy or small diff.account, after that click on process open items then system will show the difference 0 and simulate the document, here system will post gain/loss exchange GL postings along with other line items. After save the document, manually pass journal entry to dummy account and gain/loss account. I have explained clearly in the below example.
Invoice is in USD - 1000 & INR - 60000
Payment is in INR - 60000
Now I am going to clear these in INR currency in F-44 on 31.03.2015. On this date the exchange rate for USD is 60.10. At the time of clearing system will post the below entry
Vendor A/c Dr 60000 (invoice)
Vendor A/c Cr 60000 (Payment)
Gain from exchange rate A/c Cr 100 (60000 - 60100)
Small diff.write off A/c (or) Dummy A/c Dr 100
After done the above posting, we have to pass below manual JV in FB01
Gain from exchange rate A/c Dr 100
Small diff.write off A/c (or) Dummy A/c Cr 100
Regards,
Mukthar -
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
Maybe you are looking for
-
What are the roles in CRM implementation Project(all generic extractions)
Hi Gurus, Now I am placed from a support project from BW (CRM) implementation project(all are generic extractions). & I am also new to implementation project. what are the neccessary steps to be taken when we are implementing BW for CRM. Gurus please
-
Add Folder to Library - No dialog box to select folder
Hi, I wanted to designate a specific folder as the folder where iTunes / my iPhone should import music from. I want to limit iTunes to a specific folder as do not want comingle my Zune data as I have 100 gig of music which will not fit on my 32G 3GS.
-
How to upgrade Stellent 7.5.1 to Oracle Content Server 10gR3
Hi, I need to upgrade Stellent 7.5.1 to OCS 10gR3. Can someone provide the steps. Do I need to install OCS 10gR3 and then migrate the folders and content how do I migrate all the folder, content to 10gR3. Is there any documentation, blogs, steps that
-
How to calculate variance in process order?
hi i hav standard report ME1P, i need to do some modifications in this standard prgrm i did all modifications except variance calculation... can any one expln me the logic of below code? IF xeipa-lprei IS INITIAL. IF xeipa-peinh NE 0.
-
Anyone used BAPI/FM for LT03 create transfer order
Hi all, Has anyone used BAPI/FM for <b>LT03</b> create transfer order based on delivery. the BAPI/FM should accept <b>multiple line items for individual storage units</b>. thanks, Subba