Functionality
You can use this method to create and post incoming invoices.

When passing on the header data, you use the INVOIC_IND field to determine whether the system posts a credit memo or an invoice. If you leave the field initial, the system posts a credit memo. If you enter an X, the system posts an invoice.

If you want to enter an invoice for a returns order, you must leave the INVOICE_IND field initial.

As in the online transaction, the system updates the purchase order history and stock valuation data in Materials Management. The system creates accounting documents in Accounting.

You can use this method to:

Enter and post invoices with multiple account assignment
Change the account assignment of invoices, add account assignments, and post the invoices
Enter invoices for blanket purchase orders
Enter and post invoices for purchase orders containing planned delivery costs
Enter and post invoices containing unplanned delivery costs
Enter and post subsequent debits/credits
Use document types with external number assignment
Enter and post invoices with withholding tax
Enter and post invoice with more than one vendor line and different payment methods and terms of payment
Enter and post invoices for returns orders
Enter and post invoices for transportation service providers
Enter and post invoices for external service orders
Post to G/L accounts
Post to material accounts
Enter and post invoices for a one-time vendor
Enter and post invoices with a different payee
Restrictions

The following fields in Financial Accounting are not passed on:

ISR number (ISR = inpayment slip with reference number)
Bank details
Payment reference
House bank ID
Notes
The following authorization object is checked using activity 01:

M_RECH_WRK: Authorization to create invoices in certain plants
Transfer

You use the structure HeaderData to pass on the header data of the incoming invoice.

You pass on the address data of a one-time vendor or a different invoice payee with the structure AddressData.

Tables ItemData and AccountingData contain the invoice item data. The table TaxData contains the tax information for the invoice.

The tables ItemData and AccountingData contain the item data of the incoming invoice. The TaxData table contains the tax information on the invoice.

The table GlAccountData contains data for posting to a G/L account and the MaterialData table contains data for posting to a material account.

You can use the table WithTaxData to pass on withholding tax information.

Via the table VendorItemSplitData,  you can distribute the gross amount among several creditor lines with different payment methods and terms of payment.

Return

The document number of the invoice document and the fiscal year are returned by the system as key fields of the incoming invoice.

Return messages

Messages are returned in the Return parameter. The parameter documentation shows the return codes and their meanings.

Further information
The method can only perform your function if no error messages were generated in the Return table. This is the case if the header data and all the items were processed successfully.

Transaction control is not implemented. The calling program therefore has to execute the Commit Work itself after this method has been successfully invoked (in other words, if no errors were reported in the Return parameter).

Example: Incoming Invoice
This example shows the header data that you need to enter in table Headerdata and the item data that you need to enter in table Itemdata to post an invoice.

Purchase order: 10 pc of material A @ $10/pc
Goods receipt:  10 pc of material A

You receive an invoice against this purchase order referencing PO number 4500007491, PO item 10, for a quantity of 10 pc of material A and an amount of $116, including 16% VAT. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 05.20.2000
PSTNG_DATE (Posting date): 05.23.2000
COMP_CODE (Company code): 1000
GROSS_AMOUNT (Gross amount): 116.00
CURRENCY (Currency key): USD
CALC_TAX_IND (Calculate tax): X
ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (Purchase order number): 4500007491
PO_ITEM (Purchase order item): 00010
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 100
QUANTITY (Quantity): 10
PO_UNIT (Unit of measure): PC
For more information, see the parameter documentation for tables HeaderData and Itemdata.

Example: Incoming invoice in foreign currency, goods-receipt-based invoice verification and tax information
This example specifies the header data that you need to enter in table Headerdata, the item data that you need to enter in table Itemdata and the tax information that you need to enter in table TaxData to post an invoice in a foreign currency.

Purchase order:       10 pc of material A @ $10/pc
First goods receipt:  4 pc of material A
Second goods receipt: 6 pc of material A

You receive an invoice against this purchase order referencing PO number 4500007505, PO item 10, goods receipt document 50010095, 2000, item 1. The invoice is for a quantity of 4 pc of material A, a gross amount of $46.60 and 16% tax ($6.60). Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 05.20.2000
PSTNG_DATE (Posting date): 05.23.2000
COMP_CODE (Company code): 1000
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 46.60
ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (Purchase order number): 4500007505
PO_ITEM (Purchase order item): 00010
REF_DOC (Goods receipt document): 50010095
REF_DOC_YEAR (Fiscal year of current period): 2000
REF_DOC_ITEM (Goods receipt document item): 1
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 40.00
QUANTITY (Quantity): 4
PO_UNIT (Unit of measure): PC
TaxData table

TAX_CODE (Tax code): VN
TAX_AMOUNT (Tax amount in document currency): USD 6.60
For more information, see the parameter documentation for tables HeaderData, ItemData, and TaxData.

Example: Incoming invoice for blanket purchase order
This invoice shows which header data you need to enter in the table HeaderData, which item data you need to enter in the table ItemData, and which account assignment data you need to enter in table AccountingData to post an incoming invoice for a blanket purchase order.

You receive an invoice in respect of the blanket purchase order 4500015172, item 10 for an amount of $110 including 10% VAT. You want to apportion the invoice amount to the cost centers 1200 and 1500. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 02.19.2001
PSTING_DATE (Posting date): 02.21.2001
COMP_CODE (Company code): 1000
GROSS_AMOUNT (Gross amount): 110
CURRENCY (Currency): USD
CALC_TAX_IND (Calculate tax): X
ItemData table

INVOICE_DOC_ITEM (Item in the invoice document): 00001
PO_NUMBER (PO number): 4500015172
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 100
AccountingData table

1st line: Change account assignment data

INVOICE_DOC_ITEM (Document item in invoice document): 0001
SERIAL_NO (Serial number for the accont assignment): 01
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 30
GL_ACCOUNT (G/L account number): 890000
COSTCENTER (Cost center): 1200
2nd line: Add unplanned account assignment

INVOICE_DOC_ITEM (Document item in invoice document): 0001
XUNPL (Unplanned acct. assignment from IV): X
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 70
GL_ACCOUNT (G/L account number): 890000
COSTCENTER (Cost center): 1500
In the case of the blanket purchase order, the following fields for quantities and units of measure must not be populated in the tables ItemData and AccountingDataAccountingData:

Quantity (QUANTITY)
PO_UNIT (PO unit of measure)
PO_UNIT_ISO (PO unit of measure in ISO code)
PO_PR_QNT (Quantity in PO price unit of measure)
PO_PR_UOM (PO price unit of measure)
PO_PR_UOM_ISO (PO price unit of measure in ISO code)
More information is available in the parameter documentation for the tables HeaderData, ItemData, and AccountingData, and in the SAP Library under Logistics Invoice Verification.

Example: Change account assignments and add unplanned assignments
This example shows the header data that you need to enter in table Headerdata, the item data that you need to enter in table Itemdata, and the account assignment information that you need to enter in table AccountingData to change, add, and post account assignments for an invoice. If you want to change or add account assignments, there must be a non-valuated goods receipt or no goods receipt in the system. Goods-receipt-based invoice verification is specified.

Purchase order: 300 pc of material A @ $1.00/pc
Goods receipt:  300 pc of material A

This purchase order is subject to account assignment. You receive an invoice for it, referencing the PO number 4500006846, PO item 10, goods receipt document 50008849, 2000, item 1. The invoice is for a quantity of 100 pieces of material A, with a gross invoice amount of USD 116.00, including 16% VAT. You want to change the planned account assignment for the second account assignment item and add an unplanned account assignment. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 08.05.2000
PSTNG_DATE (Posting date): 08.08.2000
COMP_CODE (Company code): 1000
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 17.40
CALC_TAX_IND (Calculate tax automatically): X
PMNTTRMS (Terms of payment key): 0001
ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (Purchase order number): 4500006846
PO_ITEM (Purchase order item): 00010
REF_DOC (Goods receipt document): 500008849
REF_DOC_YEAR (Fiscal year of current period): 2000
REF_DOC_ITEM (Goods receipt document item): 1
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 100
QUANTITY (Quantity): 100
PO_UNIT (Unit of measure): PC
AccountingData table

Line 1: Change second account assignment item

INVOICE_DOC_ITEM (Invoice document item): 0001
SERIAL_NO (Account assignment serial number): 02
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Amount in document currency): 10.00
QUANTITY (Quantity): 10
PO_UNIT (Order unit): PC
GL_ACCOUNT (G/L account number): 890000
COSTCENTER (Cost center): 1200
Line 2: Add unplanned account assignment

INVOICE_DOC_ITEM (Invoice document item): 0001
XUNPL (Unplanned account assignment in Invoice Verification): X
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Amount in document currency): 5.00
QUANTITY (Quantity): 5
PO_UNIT (Order unit): PC
GL_ACCOUNT (G/L account number): 890000
COSTCENTER (Cost center): 1200
More information is available in the parameter documentation for the tables HeaderData, ItemData, and AccountingData and in the SAP Library under Logistics Invoice Verification.

Example: Incoming invoice with planned delivery costs
This examples shows the header data that you need to enter in table HeaderData, the item data that you need to enter in table ItemData, and the tax information that you need to enter in table TaxData to post an invoice containing planned delivery costs.

Purchase order: 100 pc of material A @ $1.00/pc
Goods receipt:  100 pc of material A

You receive an invoice for this purchase order referencing PO number 4500006986, PO item 10, for a quantity of 100 pieces of material A and $136.00, including 16% VAT and $20.00 planned delivery costs. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 08.10.2000
PSTNG_DATE (Posting date): 08.12.2000
COMP_CODE (Company code): 1000
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 136,00
ItemData table

Line 1: Posting the purchase order item

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (Purchase order number): 4500006986
PO_ITEM (Order item): 00010
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 100.00
QUANTITY (Quantity): 100
PO_UNIT (Unit of measure): PC
Line 2: Posting the planned delivery costs

INVOICE_DOC_ITEM (Invoice document item): 00002
PO_NUMBER (Order number): 4500006986
PO_ITEM (Order item): 00010
ITEM_AMOUNT (Item amount): 20.00
QUANTITY (Quantity): 100
PO_UNIT (Unit of measure): PC
COND_TYPE (Condition type): FRB1
TaxData table

TAX_CODE (Tax code): VN
TAX_AMOUNT (Tax amount in document currency): 16.00
For more information, see the parameter documentation for tables HeaderData, ItemData, and TaxData.

Example: Incoming invoice with withholding tax
This example shows which header data you can enter in the table HeaderData, which item data you can enter in the table Itemdata, and which withholding tax information you can enter in the table WithTaxData in order to park an incoming invoice with withholding tax.

Purchase order: 10 pc of material A @ $10

Goods receipt: 10 pc of material A

You receive an invoice for this purchase order referencing PO number 4500007505, PO item 10, GR document 50010095 2000, item 1. The invoice is for a quantity of 10 pc and a gross amount of $100. You have to pay 10% withholding tax on the gross amount. Enter the following data:

HeaderData table

INVOICE_IND (Invoice/Credit memo): X
DOC_DATE (Document date): 05.20.2000
PSTNG_DATE (Posting date): 05.23.2000
COMP_CODE (Company code): WT01
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): $100
ItemData table

INVOICE_DOC_ITEM (Item from invoice document): 00001
PO_NUMBER (PO number): 4500007505
PO_ITEM (PO item): 00010
REF_DOC (GR document): 50010095
REF_DOC_YEAR (Fiscal year of the current period): 2000
REF_DOC_ITEM (Item in a GR document): 1
TAX_CODE (Tax code): V0
ITEM_AMOUNT (Item amount): $100
QUANTITY (Quantity): 10
PO_UNIT (Unit of measure): PC
WithTaxData table

SPLIT_KEY (Grouping key for withholding tax split): 0001
WI_TAX_TYPE (Code for withholding tax type): R1
WI_TAX_CODE (Withholding tax code): 01
WI_TAX_BASE (Withholding tax base amount): 100
WI_TAX_AMT (Withholding tax amount in doc. currency): 10.00
For more information, see the parameter documentation for the tables HeaderData, ItemData, and WithTaxData.

Example: Incoming invoice with amount split
This example shows you which header data you can enter in the HeaderData table, which item data you can enter in the Itemdata table, and which information you can enter in the VendorItemSplitData table to create an incoming invoice with amount split.

Purchase order: 10 pc of material A @ $10

Goods receipt: 10 pc of material A

You receive an invoice for this purchase order referencing PO number 4500007505, PO item 10, GR document 50010095, item 1. The invoice is for a quantity of 10 pieces and a gross amount of $100. You want to apportion the gross amount to two creditor lines. 40% of the gross amount is to be paid immediately by check, and 60% of the gross amount is to be paid within 14 days, taking into account a 3% cash discount. Enter the following data:

HeaderData table

INVOICE_IND (Invoice/Credit memo): X
DOC_DATE (Document date): 05.20.2000
PSTNG_DATE (Posting date): 05.23.2000
COMP_CODE (Company code): 0001
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 100.00
ItemData table

INVOICE_DOC_ITEM (Item from the invoice document): 00001
PO_NUMBER (PO number): 4500007505
PO_ITEM (PO item): 00010
REF_DOC (GR document): 50010095
REF_DOC_YEAR (Fiscal year for the current period): 2000
REF_DOC_ITEM (Item from a GR document): 1
TAX_CODE (Tax code): V0
ITEM_AMOUNT (Item amount): 100
QUANTITY (Quantity): 10.00
PO_UNIT (Unit of measure): PC
VendorItemSplitData table

1st creditor line

SPLIT_KEY (Grouping key for split in the vendor line): 0001
SPLIT_AMOUNT (Gross invoice partial amount in doc. currency): 40.00
PYMT_METH (Payment method): S
TAX_CODE (Tax code): V0
PMNTTRMS (Payment terms key): 0001
2nd creditor line

SPLIT_KEY (Grouping key for split in the vendor line): 0002
SPLIT_AMOUNT (Gross invoice partial amount in doc. currency): 60.00
PYMT_METH (Payment method): U
TAX_CODE (Tax code): V0
PMNTTRMS (Payment terms key): 0003
For more information, see the parameter documentation for tables HeaderData, ItemData, and VendorItemSplitData.

Example: Incoming Invoice with G/L and Material Account Posting
This example shows you which data you have to provide in order to enter and post an incoming invoice (header data in table HeaderData, item data in table ItemData, G/L account information in table GlAccountData, and material account information in table MaterialData).

You receive an invoice with reference to PO number 4500006846, PO item 10. The invoice is for a quantity of 100 PC of material A, a gross amount of 150.80 USD incl. 16% tax. Included in this is a G/L account posting of 10 USD to account 400000 in company code 1, and a material account posting to the material MAT01n for 20 USD.

Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_DATE (Document date): 08.05.2000
PSTNG_DATE (Posting date): 08.08.2000
COMP_CODE (Company code): 1000
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 150.80
CALC_TAX_IND (Automatically calculate tax): X
PMNTTRMS (Payment terms key): 0001
ItemData table

INVOICE_DOC_ITEM (Invoice document item): 00001
PO_NUMBER (PO number): 4500006846
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): VN
ITEM_AMOUNT (Item amount): 100
QUANTITY (Quantity): 100
PO_UNIT (Unit of measure): PC
GlAccountData table

INVOICE_DOC_ITEM (Document item in invoice document): 00001
GL_ACCOUNT (G/L account): 400000
ITEM_AMOUNT (Item amount): 10,00
DB_CR_IND (Debit/credit indicator): S
COMP_CODE (Company code): 0001
TAX_CODE (Tax code): VN
COSTCENTER (Cost center): 1
MaterialData table

INVOICE_DOC_ITEM (Document item in invoice document): 0001
MATERIAL (Material): MAT01
PLANT (Valuation area): 0001
DB_CR_INP (Debit/credit indicator): S
ITEM_AMOUNT (Item amount): 10.00
QUANTITY (MENGE_D): 1
PO_UNIT (PO quantity unit of measure): PC
TAX_CODE (Tax code): VN
More information is available in the parameter documentation for the tables HeaderData, ItemData, GlAccountData and MaterialData and in the SAP Library under Logistics Invoice Verification.

Example: Invoice for a purchase order for external services and service-based invoice verification
This example shows you which header data you must enter in the table HeaderData, which item data you must enter in the table ItemData, and which account assignment data you must enter in the table AccountingData in order to enter and post an incoming invoice.

You receive an invoice referencing PO number 4500000191, PO item 10. Two services, A and B, are invoiced, each with a quantity of six service units. Service A has a gross amount of 580 euros incl. 16% VAT. Service B has 812 euros incl. 16% VAT. Service A has an account assignment of 50% to each of the two cost centers 1000 and 2000. Service B also has a 50-50 account assignment, to cost centers 1000 and 3000. The service acceptance is performed jointly for both services in one service entry sheet, number 1000000022. You cannot change the account assignments. Enter the following data:

HeaderData table

INVOICE_IND (Post invoice/credit memo): X
DOC_TYPE (Document type): RE
DOC_DATE (Document date): 01.10.2002
PSTNG_DATE (Posting date): 01.10.2002
COMP_CODE (Company code): 0001
CURRENCY (Currency key): USD
GROSS_AMOUNT (Gross amount): 1392.00
CALC_TAX_IND (Calculate tax automatically): X
PMNTTRMS (Payment terms key): 0001
ItemData table

First entry for service A:

INVOICE_DOC_ITEM (Item in invoice document): 000001
PO_NUMBER (PO number): 4500000191
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 250.00
QUANTITY (Quantity): 1
PO_UNIT (Unit of measure): SU
SHEET_NO (Service entry sheet number): 1000000022
SHEET_ITEM (Line number): 10
Second entry for service A:

INVOICE_DOC_ITEM (Item in invoice document): 000002
PO_NUMBER (PO number): 4500000191
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 250.00
QUANTITY (Quantity): 3
PO_UNIT (Unit of measure): SU
SHEET_NO (Entry sheet number): 1000000022
SHEET_ITEM (Line number) : 10
First entry for service B:

INVOICE_DOC_ITEM (Item in invoice document): 000003
PO_NUMBER (PO number): 4500000191
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 350.00
QUANTITY (Quantity): 3
PO_UNIT (Unit of measure): SU
SHEET_NO (Entry sheet number): 1000000022
SHEET_ITEM (Line number) : 20
Second entry for service B:

INVOICE_DOC_ITEM (Item in invoice document): 000004
PO_NUMBER (PO number): 4500000191
PO_ITEM (PO item): 00010
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Item amount): 700.00
QUANTITY (Quantity): 1
PO_UNIT (Unit of measure): SU
SHEET_NO (Service entry sheet number): 1000000022
SHEET_ITEM (Line number) : 20
AccountingData table

First account assignment for service A:

INVOICE_DOC_ITEM (Document item in invoice document): 000001
SERIAL_NO (Sequential number of the account assignment): 01
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 250.00
QUANTITY (Quantity): 3
PO_UNIT (PO unit of measure): SU
Second account assignment for service A:

INVOICE_DOC_ITEM (Document item in invoice document): 000001
SERIAL_NO (Sequential number of the account assignment): 02
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 250.00
QUANTITY Quantity): 3
PO_UNIT (PO unit of measure): SU
First account assignment for service B:

INVOICE_DOC_ITEM (Document item in invoice document): 000003
SERIAL_NO (Sequential number of the account assignment): 01
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 350.00
QUANTITY (Quantity): 3
PO_UNIT (PO unit of measure): SU
Second account assignment for service B:

INVOICE_DOC_ITEM (Document item in invoice document): 000004
SERIAL_NO (Sequential number of the account assignment): 03
TAX_CODE (Tax code): V1
ITEM_AMOUNT (Amount in document currency): 350.00
QUANTITY (Quantity): 3
PO_UNIT (PO unit of measure): SU
More information is available in the parameter documentation for the tables HeaderData, ItemData, and AccountingData, and in the SAP Library under Logistics Invoice Verification.

Example: Incoming invoice for one-time vendor
This example shows you how to proceed in order to enter and post an invoice for a one-time vendor.

You do not need to enter data in the AddressData table. If you do not enter data in the AddressData table, the address data for the one-time vendor is adopted 1:1 in the invoice from the purchase order.

If you use table AddressData to transfer data, the address data for the one-time vendor is read from the purchase order into the invoice and is then either overwritten or supplemented by the fields of table AddressData.

The purchase order for the one-time vendor has the following stored data: Name ‘SAP AG’, postal code ’60000′ and street and building number ‘Neurottstraße 16′. You receive an invoice with the one-time vendor address: Name ‘SAP AG’, postal code ’69190′, and place ‘Walldorf’. Enter the following data:

AddressData table

ACC_1_TIME (Indicator one-time vendor): X

NAME (Name): SAP AG

POSTL_CODE (Postal code): 69190

CITY (Place): Walldorf

The invoice is posted with the following one-time vendor: Name ‘SAP AG’ street and building number ‘Neurottstraße 16′, postal code ’69190′, city ‘Walldorf’.

For more information, see the parameter documentation for the table AddressData.

Example: Incoming invoice for different payee
This example shows you which address data you must enter in the table AddressData to enter and post an invoice for a different payee.

You receive an invoice for the different payee with name ‘SAP AG’, postal code ’69190′, place ‘Walldorf’, bank number ’38070724′ and account number ’4711′.

Enter the following data:

AddressData table

ACC_1_TIME (Indicator one-time vendor): ‘ ‘

NAME (Name): SAP AG

POSTL_CODE (Postal code): 69190

CITY (Place): Walldorf

BANK_NO (Bank number): 38070724

BANK_ACCT (Bank account number): 4711

For more information, see the parameter documentation for the table AddressData.

Parameters
HEADERDATA
ADDRESSDATA
INVOICEDOCNUMBER
FISCALYEAR
ITEMDATA
ACCOUNTINGDATA
GLACCOUNTDATA
MATERIALDATA
TAXDATA
WITHTAXDATA
VENDORITEMSPLITDATA
RETURN
EXTENSIONIN

Exceptions
Function Group
MRM_BAPI

ADR6 = ADDRESS NUMBER
LFA1 = VENDOR
WYT3 = PARTNER FUNCTION TABLE

select adr6-addrnumber (email)

from table adr6 join table lfa1 with key adr6-addrnumber = lfa1-adrnr

ABAP Version :

data : lv_email like adr6-addrnumber.

select addrnumber into lv_email

from adr6 as a inner join kna1 as b on a~addrnumber = b~adrnr.

1. You must maintain email address in vendor master data.

2. The same applies to your user master data. For the output type for default values, a communication strategy needs
to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the
Customizing via the following path:

(SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy).

As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).

3. Use the standard SAP environment (program ‘SAPFM06P’, FORM routine ‘ENTRY_NEU’ and form ‘MEDRUCK’) as the processing routines.

4. In the condition records for the output type (for example, Transaction MN04), use medium ’5′ (External send).

5. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.

6. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.

● As a text file to the SAP GUI working directory

● Unconverted or as a table, RTF, or HTML to a directory of your choice

● As a PDF file to a directory of your choice

Procedure
Exporting to the SAP GUI Working Directory
If you are exporting large quantities of data, downloading the spool request as a text file to the SAP GUI working directory is a good solution.

Choose Spool Request ® Forward® Export as Text.

The entire text is stored in your SAP GUI working directory in ASCII format.

A file of this type is named using the following pattern:

.txt

Example: ABC0000004327.txt

You require appropriate authorization from your administrator for this function.

Exporting Unconverted or as a Table, RTF, or HTML to a Directory of Your Choice
The contents of the spool request are first displayed. You then download the contents in the format of your choice to a directory of your choice.

…

1. Select the spool request to be exported and choose Display Contents.

2. For SAPscript/Smart Forms documents, activate the list display by choosing Goto.

3. Choose System ® List ® Save ® Local File.

4. Select a format and confirm your choice.

5. Select a directory and save the spool request.

By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

Exporting as PDF File
You want to export the contents of a spool request as a PDF file to a directory of your choice, and print the file. The PDF file contains the print data in the format in which it will be output by the printer.

The following procedure is irrelevant when printing PDF-based forms, since a PDF file is already returned with this method. See also Displaying and Printing PDF-Based Forms.

You also require authorization from your administrator to run this report.

The PDF file is generated as follows with report RSTXPDFT4:

…

1. Generate a spool request from the document to be printed.

2. In transaction SE38, start report rstxpdft4.

3. In the displayed window, enter the spool request number and the directory in which the PDF file is to be stored.

Leave the Download PDF File option selected.

Choose Execute.

4. In the next window, confirm or change the path where the file is be stored.

Save your entries.

5. The system displays a log from which you can see whether the report was successfully performed.

You can then open the file from the directory and print it.

Restrictions for Exporting as a PDF File
● The PDF conversion only supports true bar codes for Smart Forms, which were generated with the new bar code technology with SAP NetWeaver 2004. In all other cases, the bar code is only simulated.

● PDF conversion, especially of ABAP lists, is slower and is therefore not suitable for mass printing. However, you can speed up the conversion to PDF using the FASTLISTCONV option in report RSTXPDF3.

● The font selection for ABAP lists is predefined in the PDF converter and cannot be changed.

For more information about constraints, see SAP Note 323736 on the SAP Service Marketplace.

BAPI & PR RELEASE
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/12729%3Fpage%3Dlast%26x-showcontent%3Doff

Report RM06BBIX fills this field. It only has to be run once when you switch from the old release procedure to the new one.
If you have requisitions covered by the old release procedure in your system, and you wish to convert to the new one, run report RM06BBIX by clicking on "Execute report".

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

This correction and approval procedure is intended to allow material, quantity, delivery date, account assignment, and source of supply to be checked for correctness.
As of Release 3.0 there is a new release procedure, which works with MM Classification. This allows the existing release conditions "value", "material group", "account assignment" and "plant" to be considerably extended and the procedure to be made more flexible.
The new procedure allows the release not only of requisitions but also of the purchasing documents "request for quotation (RFQ)", "purchase order (PO)", "contract", "scheduling agreement" and "service entry sheet".
With regard to requisitions, both the new and the old release procedures are available on a parallel basis.
The aim of this release procedure for purchasing documents is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle. The person responsible processes the relevant document in the system, thereby marking it with an "electronic signature" which can give the the document legal force. In contrast to the previous release procedure for requisitions, the new one therefore only permits purchasing documents to be released in total: there is no provision for partial approval on an item by item basis.
Using the release system with MM Classification
If the release procedure is used with Classification, release strategies can be determined for purchasing documents with the aid of characteristics. Accordingly, a new class type is available for the release procedure. Each of the different documents has its own class. For instance, there is a class for requisition release procedures and a class for the release of service entry sheets. Each class can have its own characteristics, thereby allowing each document to be automatically assigned to a certain release strategy on the basis of its characteristic values. The characteristic values from the document are passed on to MM Classification with the aid of communication structures.
Changes made to documents after the start of the release procedure
If changes are made to purchasing documents for which the release procedure has already started, the system always issues an appropriate message to the user. There are three types of change:

• Case 1: insignificant change that does not necessitate another release strategy.

• Case 2: relevant change that does not necessitate another release strategy.

• Case 3: relevant change that necessitates another release strategy.

Alternative release
The release procedure can also allow for alternatives.

If, for instance, a release strategy has five release points in an ascending hierarchy of 1 to 5, and the highest hierarchy level has released the document, all four subordinate release points do not necessarily also have to release it.
The box with the information on the release strategy additionally offers you the possible alternatives for selection. For example, either the points 1, 2, 3, and 4 must approve the item, or – alternatively – release point 5.
Link to workflow
With the link to SAP workflow, release points are automatically made aware (by e-mail) of purchase requisitions requiring approval. In Customizing, you define which release points participate in the workflow.
The procedure is as follows:
Release point 1, which the first one that has to release a requisition, receives an e-mail notification that requisition no. 12345 is awaiting release.
In processing the mail, the user can release or refuse approval for the requisition.
When release point 1 has finished processing, the following release point receives an e-mail. The process is repeated until the requisition has been seen by all the release points that have been assigned to a release strategy.
A precondition is that the release points involved must be flagged as relevant to workflow.
SAP recommendation:
In particular, you can use workflow for those release points (individuals or departments) that, as a rule, are not involved in day-to-day approval processes and therefore may not be aware of requisitions that are awaiting release. For example, release points 1 to 5 approve requisitions on a daily basis. Requisitions that exceed a value of $ 500,000 have to be approved by a member of the board of management. The latter can be made aware of the existence of any such requisitions via e-mail.
Change system parameters in customizing
Database index for document selection
Prior to Release 3.0, the data for the collective release of purchase requisitions had to be regularly updated. For this purpose, it was necessary for the system administrator to recompile the matchcode.
If you change over to the new release procedure for purchasing documents, this is unnecessary because there is a database index which selects requisitions to be released.
To permit the requisitions requiring release to be found via the database index, release information from existing requisitions is taken over into a new field "Subject to release".
Report RM06BBIX fills this field. It only has to be run once when you switch from the old release procedure to the new one.
If you have requisitions covered by the old release procedure in your system, and you wish to convert to the new one, run report RM06BBIX by clicking on "Execute report".
Execute report
New field "Release group"
In Customizing, there is a new field "Release group" with which the release strategies are uniquely identified. This allows you to extend the code for the release strategy (to date, two characters long) to four characters, for example, as follows:
- 01-S1 = strategy S1 for purchase requisitions
- 02-S1 = strategy S1 for other purchasing documents
The document type must be assigned to a release group with the aid of the object type. The latter specifies for which purchasing document a release group is valid, e.g. object type 1 (requisition) belongs to group 01 (requisitions).
The following object types are available in the standard system:

• 1 purchase requisition

• 2 purchase order

• 3 service entry sheet

• 4 reserve

For more on this topic, please refer to
Set up procedure without classification.
USER EXITS
The following USER EXITS are available to enable you to adjust the process of determining the release strategy to suit your requirements:

• M06B0001

  To determine the person in workflow responsible for requisition approval.

• M06B0002

  To change the process of determining the release strategy for purchase requisitions

• M06E0002

  To change the process of determining the release strategy for other purchasing documents

M06B0001
The USER EXIT is called up if a release code has the workflow indicator "9". Objects from human resources planning can be passed on as "persons responsible": e.g. "US" (user) in the field "Object type" and a user name in the field "Processor’s ID".
Example of determination of person responsible via customer-specific table: you can create a customer-specific Customizing table along the lines of T16FW, via which the person responsible is determined on the basis of the characteristics "release group", "release code" etc.
Example of determination of person responsible via cost center: The cost center can be read and the person responsible for the cost center used as person responsible for release purposes via the requisition account assignment.
M06B0002
With this USER EXIT you can change the communication structure for the determination of the release strategy for the requisition.
Examples:
1. Filling of user fields in CEBAN
The following user fields are available:
USRC1

USRC2

USRN1

USRN2
Furthermore, the communication structure CEBANZZ is available, enabling you to apply your own fields.
The cost center master record can be read via the cost center in the communication structure and the person responsible for the cost center set in the user field USRC1.
If the class for the determination of the requisition release strategy contains a characteristic with reference to CEBAN-USRC1, the strategy is determined as a function of the person responsible for the cost center.
2. Changing standard fields in CEBAN
If the value of the requisition used for the determination of the strategy in the standard SAP system is not to be used, the value can be calculated on a customer-specific basis. The field CEBAN-GSWRT can then be overwritten with this value.
If the class for the determination of the requisition strategy now contains a characteristic with reference to CEBAN-GSWRT, the strategy is determined as a function of the changed value.
M06E0002
With this USER EXIT you can change the communication structure for determining the release strategy for purchasing documents.
The following user fields are available:
USRC1

USRC2

USRN1

USRN2
Furthermore, the communication structure CEKKOZZ is available, enabling you to apply your own fields.
Further notes
There is a new authorization object M_EINK_FRG for the release procedure for purchasing documents. The authorization object contains the release group and the release code.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

DEBIT VENDOR = I HAVE TO GET MONEY FROM HIM
CREDIT VENDOR = YOU HAVE TO GIVE HIM MONEY

1. Go To Accounts common TCODE – FKMN
2. Choose FK10N

Following Screen is displayed.

Following Screen is Displayed.

FOLLOWING REPORT IS DISPLAYED.

Check this details from workflow log or you can use either of the 2 Function Modules

SWL_GET_PROCESS_STEPLIST
SWP_WORKFLOW_LOG_READ

You have to look for the AAGENT field that stores the actual agent User Id.

Whether it is approved or rejected you can use FM SAP_WAPI_DECISION_READ

FM attached to the function module is BAPI_IDOC_INPUT1

Go to We82 and enter the idoc Type which is Above you will get the message type Related to Idoc type..

Go to We41 – for Outbound Process code
We42- for INbound Process codes

Go to we57 – to see the Function modules attached to Idoc type and Message Type.

Posted: May 8, 2009 6:54 AM in response to: Sunil Brg Reply

Hi,
As your requirement was to create an Inbound Purchase Order.
The simple way is:

use Message type either PORDCR (Create purchase order) or PORDCR1 (Create purchase order).
Basic Idoc Type : PORDCR05
Inbound processing Function Module for above IDOcs is: IDOC_INPUT_PORDCR.
The above said function module internally uses BAPI "BAPI_PO_CREATE" to create PO.

However, to satisfy the requirement completely, you need to create a Z-Process Code and attach IDOC_INPUT_PORDCR function module to the Z-Process Code created.
Then we can use this new Z-process code in our partner profile.

Step-by-Step process to create Process Code (Inbound):

1. First Maintain WE57 transaction:
Go to WE57 transaction and search for function module IDOC_INPUT_PORDCR.
If found, WE57 NOT required to maintain.

If not found,
Go to Change mode. Then NEW ENTRIES

Pass following parapets and save it.
FunctionModule: IDOC_INPUT_PORDCR
Fucntion Type: Function Module
Basic Type: PORDCR05
Message Type: PORDCR

2. Maintain BD51 transaction
Go to BD51 transaction and search for function module IDOC_INPUT_PORDCR.
If found, BD51 NOT required to maintain.

If not found,
Go to Change mode. Then NEW ENTRIES

Pass following parametrs and save it.
Function Module (Inbound) : IDOC_INPUT_PORDCR
Inout Type: 0

. Maintain WE42 transaction (Inbound Process Codes):

Go to WE42 transaction.
Go to Change mode. Then NEW ENTRIES

Pass following parapets as screen shot attached.
Process Code: ZPUR (Change as your coding standards)
Description : Create Purchase Order (Inbound)

Option ALE:
Choose “Processing with ALE Service”.

Processing Type:
Choose “Processing by Function Module”.

Now SAVE the Application: After SAVE function module will be populated automatically into Identification ID field

Now Maintain your Partner Profiile.

For ORDERS05 is outbound processing and PORDCR101 is for inbound processing, as structure is different you have to use an EAI tool (XI or others) in order to do the mapping between outbound and inbound.

I’m using both ORDERS04 in order to send PO to vendors, but a mapping is done in order to communicate in EDIFACT or Html and PORDCR01 in order to do inbound replication of PO from SRM to SAP backend (Again a mapping is needed)

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

Hi There,

I am working on a scenario where I am sending a PO from R/3 to SNC. The issue is that the Overdel Tol and Underdel Tol fields which are present in R/3 is not getting populated in idoc ORDERS05.

Please let me know what could be the reason? and which ORDERS05 segment should have these values.

Regarsd,
Nishant
***************************************************************

Hi,

as per:
http://help.sap.com/saphelp_scm70/helpdata/EN/9c/119fec6bb1469e928635938a086286/content.htm
quote:
"The transfer of delivery tolerances from an SAP back-end system up to and including enhancement package 3 for SAP ERP 6.0 is only possible with the following IDoc:
PORDCR1.PORDCR102"

so you will not see them in ORDER05 unless you use a user exist to add it there

hope this answers your question

Regards,
Michal KRawczyk
********************************************

Hi Michal,

Thanks for your valuable response.

Can I use PORDCR1.PORDCR102 instead of ORDERS.ORDERS05 for PO Collaboration in SNC

Regards,
Nishant
**********************************************

Hi,

you can use any IDOC in the output as long as you add additional mapping in XI
as the data in PORDCR is the same (PORDCR has even more) as with orders05

Regards,
Michal Krawczyk

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

Ranjan Das, president, SAP India, died of a heart attack on Wednesday. He was 42. Das had been with SAP for over eight years and moved to Mumbai [ Images
] in 2007 after taking over as Head of SAP India.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

[edit]Short Description
Create Enjoy Purchase Orders

[edit]Function Module
BAPI_PO_CREATE1

[edit]Description
[edit]Functionality
STYLE S_DOCUS1 Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction (ME21N). Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1. STYLE *

[edit]Functionality in Detail
STYLE S_DOCUS1

[edit]Authorization
The following authorization objects are checked when an Enjoy purchase order is created (activity 01):

M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
[edit]Controlling adoption of field values via X parameter
For most tables, you can determine via your own parameters in the associated X parameter in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition – you can change it with the BAPI).

[edit]Transfer
Header data
The header data of the Enjoy purchase order is transferred in the table PoHeader.

Item data
The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule. Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.

Services and limits
Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.

Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.

Vendor and delivery address
The vendor’s address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address management facility. Note In this method, the following restrictions apply with regard to addresses: Addresses can only be created with this method – they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE. When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.

Partner roles
The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").

Import/export data
Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.

Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.

Version Management
You can make use of the Version Management facility via the table AllVersions.

[edit]Return
The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.

[edit]Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. When a PO has been created successfully, the PO number is also placed in the return table with the appropriate message. STYLE * STYLE S_DOCUS1

[edit]Restrictions
With this function module, it is not possible to:

Create subcontracting components (you can only use existing ones)
Create configurations (you can only use existing ones)
Change message records (table NAST) and additional message data (this data can only be determined via the message determination
facility (Customizing))

Attach documents to the purchase order
See also further information in SAP Note 197958. STYLE *

[edit]Example
STYLE S_DOCUS1 Example of population of BAPI interface in the Function Builder Parameter: POHEADER COMP_CODE,,=,,1000 DOC_TYPE,,=,,NB ITEM_INTVL,,=,,00001 VENDOR,,=,,0000001000 PMNTTRMS,,=,, 0001 PURCH_ORG,,=,, 1000 PUR_GROUP,,=,, 001 CURRENCY,,=,, EUR Parameter: POHEADERX COMP_CODE,,=,, X DOC_TYPE,,=,, X ITEM_INTVL,,=,, X VENDOR,,=,, X PMNTTRMS,,=,, X PURCH_ORG,,=,, X PUR_GROUP,,=,, X Parameter: POITEM PO_ITEM,,=,, 00001 MATERIAL,,=,,100-100 PLANT,,=,,1000 STGE_LOC,,=,,0001 QUANTITY,,=,,15.000 TAX_CODE,,=,,V0 ITEM_CAT,,=,, 0 ACCTASSCAT,,=,,K Parameter: POITEMX PO_ITEM,,=,,00001 MATERIAL,,=,,X PLANT,,=,,X STGE_LOC,,=,,X QUANTITY,,=,,X TAX_CODE,,=,,X ITEM_CAT,,=,,X ACCTASSCAT,,=,,X Parameter: POSCHEDULE PO_ITEM,,=,,00001 SCHED_LINE,,=,,0001 DELIVERY_DATE,,=,,02.12.2002 QUANTITY,,=,,6.000 PO_ITEM,,=,,00001 SCHED_LINE,,=,,0002 DELIVERY_DATE,,=,,03.12.2002 QUANTITY,,=,,5.000 PO_ITEM,,=,,00001 SCHED_LINE,,=,,0003 DELIVERY_DATE,,=,,04.12.2002 QUANTITY,,=,,4.000 Parameter: POSCHEDULEX PO_ITEM,,=,,00001 SCHED_LINE,,=,,0001 PO_ITEMX,,=,,X SCHED_LINEX,,=,,X DELIVERY_DATE,,=,,X QUANTITY,,=,,X PO_ITEM,,=,,00001 SCHED_LINE,,=,,0002 PO_ITEMX,,=,,X SCHED_LINEX,,=,,X DELIVERY_DATE,,=,,X QUANTITY,,=,,X PO_ITEM,,=,,00001 SCHED_LINE,,=,,0003 PO_ITEMX,,=,,X SCHED_LINEX,,=,,X DELIVERY_DATE,,=,,X QUANTITY,,=,,X Parameter: POACCOUNT PO_ITEM,,=,,00001 SERIAL_NO,,=,,01 QUANTITY,,=,,15.000 GL_ACCOUNT,,=,,0000400000 COSTCENTER,,=,,0000001000 CO_AREA,,=,,1000 Parameter: POACCOUNTX PO_ITEM,,=,,00001 SERIAL_NO,,=,,01 QUANTITY,,=,,X GL_ACCOUNT,,=,,X COSTCENTER,,=,,X CO_AREA,,=,,X Parameter: POCOND ITM_NUMBER,,=,,000001 COND_ST_NO,,=,,001 COND_TYPE,,=,,PB00 COND_VALUE,,=,,79.900000000 CURRENCY,,=,,EUR CURRENCY_ISO,,=,,EUR COND_UNIT,,=,,KG COND_P_UNT,,=,,1 CHANGE_ID,,=,,U Parameter: POCONDX ITM_NUMBER,,= ,,000001 COND_ST_NO,,= ,,001 ITM_NUMBERX,,= ,,X COND_TYPE,,= ,,X COND_VALUE,,= ,,X CURRENCY,,= ,,X CHANGE_ID,,= ,,X Parameter: POPARTNER PARTNERDESC,,= ,,OA LANGU,,= ,,EN BUSPARTNO,,= ,,0000001100 PARTNERDESC,,= ,,GS LANGU,,= ,,EN BUSPARTNO,,= ,,0000001200 PARTNERDESC,,= ,,PI LANGU,,= ,,EN BUSPARTNO,,= ,,0000001000 STYLE *

[edit]Help in the Case of Problems
RESET N1 STYLE S_DOCUS1

SAP Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating specifically
to External Services Management.)

If you have detected an error in the function of a BAPI, create a reproducible example in the test data directory in the
Function Builder (transaction code SE37). SAP Note 375886 tells you how to do this.

If the problem persists, create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible
example where appropriate. STYLE *

[edit]Customer Enhancements
STYLE S_DOCUS1 The following customer exits (function modules) are available for the BAPI BAPI_PO_CREATE1:

EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following customer exits (function modules) are available for the BAPI BAPI_PO_CHANGE:

EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD). There is also the option of populating customers’ own fields for header, item, or account assignment data via the parameter EXTENSIONIN. STYLE *

[edit]Further information
RESET N1 STYLE S_DOCUS1

Further information on purchase order BAPIs is available in SAP Note 197958.
If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates
will be carried out. If you need this function, take a look at Note 420646.

The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions).
However, you can use the BAPI BAPI_PO_CHANGE for this purpose if just the document number is populated and the invoker has change authorizations for purchase orders.

Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL,
BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.

For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for
the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP Easy Access menu. STYLE *

[edit]Import
ExtensionIn
MemoryComplete
MemoryUncomplete
NoAuthority
NoMessageReq
NoMessaging
NoPriceFromPo
PoAccountProfitSegment
PoAccountX
PoAddrVendor
PoComponentsX
PoCondX
PoContractLimits
PoExpImpHeader
PoExpImpHeaderX
PoExpImpItemX
PoHeader
PoHeaderX
PoItemX
PoLimits
PoScheduleX
PoServices
PoServicesText
PoShipping
PoShippingX
PoSrvAccessValues
TestRun
Versions
[edit]Export
AllVersions
ExpHeader
ExpPoExpImpHeader
ExpPurchaseOrder
ExtensionOut
PoShippingExp
Return
[edit]Changing
PoAccount
PoAddrDelivery
PoComponents
PoCond
PoCondHeader
PoCondHeaderX
PoExpImpItem
PoItem
PoPartner
PoSchedule
PoTextHeader
PoTextItem
[edit]Pattern

CALL FUNCTION ‘BAPI_PO_CREATE1′
EXPORTING
POHEADER =
" POHEADERX =
" POADDRVENDOR =
" TESTRUN =
" MEMORY_UNCOMPLETE =
" MEMORY_COMPLETE =
" POEXPIMPHEADER =
" POEXPIMPHEADERX =
" VERSIONS =
" NO_MESSAGING =
" NO_MESSAGE_REQ =
" NO_AUTHORITY =
" NO_PRICE_FROM_PO =
" IMPORTING
" EXPPURCHASEORDER =
" EXPHEADER =
" EXPPOEXPIMPHEADER =
" TABLES
" RETURN =
" POITEM =
" POITEMX =
" POADDRDELIVERY =
" POSCHEDULE =
" POSCHEDULEX =
" POACCOUNT =
" POACCOUNTPROFITSEGMENT =
" POACCOUNTX =
" POCONDHEADER =
" POCONDHEADERX =
" POCOND =
" POCONDX =
" POLIMITS =
" POCONTRACTLIMITS =
" POSERVICES =
" POSRVACCESSVALUES =
" POSERVICESTEXT =
" EXTENSIONIN =
" EXTENSIONOUT =
" POEXPIMPITEM =
" POEXPIMPITEMX =
" POTEXTHEADER =
" POTEXTITEM =
" ALLVERSIONS =
" POPARTNER =
" POCOMPONENTS =
" POCOMPONENTSX =
" POSHIPPING =
" POSHIPPINGX =
" POSHIPPINGEXP =
.

Retrieved from "http://abap.wikiprog.com/wiki/BAPI_PO_CREATE1"
Category: BAPI PurchaseOrderFRE

Views

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

Reply

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

Reply

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

Example 1 – searching for master data using a table enhancement structure:

Select * from mara

Where color=’BLACK’ and smell = ‘GREAT’ and taste = ‘AWSOME’

Example 2 – searching for "classified" master data:

Select *

From mara t1 , Ausp t2, Ausp t3, ausp t4

where t1.matnr = t2.object

and t2.classification_type = ‘MATERIAL-COLOR’

and t2.class_value = ‘BLACK’

and t1.matnr = t3.object

and t3.classification_type = ‘MATERIAL-SMELL’

and t3.class_value = ‘GREAT’

and t1.matnr = t4.object

and t4.classification_type = ‘MATERIAL-TASTE’

and t4.class_value = ‘AWSOME’

Why is this a problem?

The first sql statement is a very simple query that accesses just one table, and provided your data has high cardinality, may benefit from a database index to make it even quicker and cheaper to execute.

The second sql, must join 4 tables. At first the database must identify which condition is the one with the best filtering, then for each qualifying row two more scan’s of AUSP must be made in order to check the additional conditions. The overall cost per row is usually significantly higher then in the first case.

Moreover, determining the tables join order is not a trivial operation since it requires identifying the best (most filtering) "condition" , and if done incorrectly (because of inadequate statistics or database code) will cause the database to do more work and increase the query cost and runtime.

Another thing to consider is that the second query doesn’t scale very well, the more "classifications" are used to locate the data the more times table AUSP will be accessed hence the run time will probably increase. In the first case, adding conditions will usually improve the queries speed.

Omer brandis
"conquered storage will not be returned"

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

Filter by Class Type. You can reduce the data set.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID0364544950DB11918610962096452866End?blog=/pub/wlg/12442%3Fpage%3Dlast%26x-maxdepth%3D0

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

http://www.10secondssoftware.com/
What is ExpressPR?
ExpressPR is a web based solution that will notify your managers via email when they have purchase requisitions to approve. Managers can access ExpressPR via their browser or mobile phone to review and approve purchase requisitions in seconds. It’s that easy!
With an installation that takes minutes and no configuration changes to your SAP R/3 system, ExpressPR will radically streamline your purchase requisition approval process.

Screenshots

Key Features

• Access ExpressPR via your desktop browser, iPhone, Blackberry or smart phone
• Zero SAP configuration required. ExpressPR integrates seamlessly with your SAP system
• ExpressPR can monitor multiple SAP release strategies
• Realtime notification of Purchase Order requisition requests – direct to your inbox
• ExpressPR has no requirement for the SAP Workflow module
• Two clicks and your purchase requisition is approved! It’s that simple.
• Installation takes minutes.

Take ExpressPR for a test drive
Request a demo account and take a look at ExpressPR in our secure test environment.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

1. Develop client applications for the SAP Server. Here you can use either RFCs or HTTP/SOAP/XML (outside-in).
2. Write RFC server applications that run in a .NET environment and can be installed starting from the SAP system (inside-out).

With Microsoft Visual Studio .NET you can:
Use the integrated Proxy Wizard to generate proxy objects.

3. Use any common programming language that has complete access to Microsoft Visual Studio .NET.
4. Link SAP tables and structure with Windows and Web form controls (Data Binding).
5. Use secure authorization methods such as Single Sign-On, Kerberos, and Microsoft Passport (www.passport.net).

Further Information

6. SAP.Net Connector: Architecture
7. Creating ASP .Net Applications using the SAP .Net Connector
8. SAP.Net Client
9. SAP.Net Server
10. SAP.Net Connector: Installation
11. SAP .Net Programmer’s Reference

For more information on the SAP .NET Connector, see the SAP Service Marketplace at the internet address:
service.sap.com

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

> If your SAP components run on the Web Application Server version 6.20 or above, you can configure e-mail via SMTP. The procedure is discussed in detail in OSS NOTE 455140: Configuration of E-Mail, fax, paging / SMS via SMTP.
If you’re running an older release, you can use the SAP Exchange Connection. It can be downloaded from the SAP Service Marketplace in the Software Distribution Center. The documentation is contained in the download package.

* Editor’s note: The SAP Service Marketplace requires a user ID

There is a program which can be scheduled to execute once in

10-15 mins, which picks up the workitems from SAP Inbox and

sends it across to external mail.

1) Please check RSWUWFML2 program and you need to schedule this

program with a proper variant.

2) Please maintain the autoforwarding for the users to whom the

workitems needs to be forwarded in SO36 transaction.

3) Schedule the program RSCONN01 which sends the mails from

SCOT transaction to external mail.

Just to make sure the workitems are send properly to external

mail id’s you can create a job with 2 steps first with program

RSWUWFML2 to get executed and program RSCONN01 to be executed

next.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

> If your SAP components run on the Web Application Server version 6.20 or above, you can configure e-mail via SMTP. The procedure is discussed in detail in OSS NOTE 455140: Configuration of E-Mail, fax, paging / SMS via SMTP.
If you’re running an older release, you can use the SAP Exchange Connection. It can be downloaded from the SAP Service Marketplace in the Software Distribution Center. The documentation is contained in the download package.

* Editor’s note: The SAP Service Marketplace requires a user ID

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

- the PO item is blocked

- the PO item is flagged for deletion

- another colleague is currently processing the purchase order

- the purchase order has not yet been released

- the corresponding service entry sheet has been deleted

- for a held invoice against planned delivery costs: the vendor in the held invoice is not the same as the vendor in the condition in the purchase order, or the same as the vendor from the purchase order history entries. This is due to the fact that the vendor in the condition in the purchase order has been changed in the meantime. In this case, the held document cannot be processed further. You can use report Z_MRM_DELETE_PP from note 501905 to delete the document.

Procedure
Check the purchase order.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

Powered by ScribeFire.

ECATT – Get more Business Documents

Powered by ScribeFire.

Quicklinks

* Home to SAP R3 Electronic Data Interchange (EDI)
* EDI Books
* EDI utilities
* IDoc interface
* IDoc Types – Message Types

* EDI Links
* XML Links
* EDI Whitepapers

Purchase order output (ORDERS and ORDCHG)
1. In the purchase order you provide one or several items with a deletion indicator. Why are these indicators not transferred via IDoc?

Deleted items are only issued with IDoc type ORDCHG. Perhaps you selected the wrong ME10 process code for the output of change messages in the partner profile. To set the partner profile correctly, consider the following question.
2. In the partner profiles for the ORDERS outgoing message, the change message was also entered.

IDoc type ORDCHG is available for the output of changes. Define the following data for the respective partner in the initial parameters:

» application : EF

» message type : enter the corresponding value here

» transaction code : ME11 (is linked to IDOC_OUTPUT_ORDCHG)

» change message : X
3. More fields are listed in the IDoc definition (WE60) than are transferred with ORDERS/ORDCHG. Why?

The order IDoc only transfers the data necessary for the creation of a sales order in the receiving system. If this data should not suffice, you can add the missing information to the IDoc using the customer function EXIT_SAPLEINM_002 or EXIT_SAPLEINM_011.

Remember that this information must also be processed on the input side correspondingly.

4. Why are not all partner roles issued from the purchase order in the segment E1EDKA1 or E1EDPA1?

Several address segments (E1EDKA1 or E1EDPA1) can be issued in the IDoc that are distinguished by qualifier values (in the PARVW field), that is, the value of the qualifier determines the contents of the data entered , for example, ‘AG’ means “Ordering party”. The allowed values of the qualifier are defined in the values list of the domain (here EDIF3035).

Incidentally, the qualifier values in the IDoc output of the purchase order are the same as the corresponding German partner roles in the purchase order.

The IDOC_OUTPUT_ORDERS and IDOC_OUTPUT_ORDCHG function modules usually only issue the following three partners:

* Ordering party with qualifier value AG (only E1EDKA1)
Data: Organizational data (purchasing organization, telephone number …), customer number for the vendor, if these are maintained in the vendor master (in the LFB1-EIKTO field)
* Vendor with qualifier value LF (only E1EDKA1)
Data: Vendor number, organizational data (sales organization, telephone number …), global location number
* Goods recipient with qualifier value WE (E1EDKA1 and E1EDPA1)
Data: Address data in accordance with SADR structure (alternatively from the plant address/address master or manual address), plant number, customer number (if a third-party purchase order)

If the goods recipient is maintained differently on the items, it is not issued at header level (segment E1EDKA1), but at item level (E1EDPA1); however, header segments and item segments may be issued, see Note 406313.

A different ordering address may be issued in the purchase order printout.

For this, you can define the partner ‘BA’ (ordering address), for example; the data for this partner is printed instead of the data for the ordering party. In the IDoc, an additional address segment E1EDKA1 is issued with the qualifier ‘BA’ that contains the vendor number of the different ordering addresses. An additional entry is required in the partner profile (Transaction WE20) for the partner role ‘BA’ and the respective partner.

From a technical point of view, when ordering addresses are different, the partner role is transferred from the message record (database table NAST, field PARVW) and the value is not checked against the value table of domain EDIF3035.

As a result of this, an E1EDKA1 segment is issued with the ‘LS’ qualifier when the partner type ‘LS’ (instead of ‘LI’) is used in the partner profile (Transaction WE20).

The data in the purchase order IDoc should be used for creating or changing a sales order in inbound processing; no further address data is usually required for that.

Nevertheless, if this is necessary, we refer you to the customer exits (SAP enhancement MM06E001).

1. In the purchase order the system issues error message VN032, which indicates that the partner profile is not correct.

In most cases, the error message is correct. Compare the data constellation specified in the error message with those you maintained in Transaction WE20. If these should differ, adjust them accordingly.

2. The system issues error message VD561 during the output of purchase orders (Partner nnn is not an EDI partner)

See Note 389713.

3. The system displays error message ME760 when you output purchase order change using EDI.

See Notes 310004 and 117450.

4. The header and item texts defined in the purchase order are not output at all or only in part (ORDERS and ORDCHG).

Check in Table T166K (Header texts) and T166P (Item texts) whether there is a corresponding entry for the combination of transaction, document type, object and text ID, as only then are the texts output in the IDoc. See Notes 446008, 410989 and 446208.

5. During the output of the texts, the system only issues 70 characters instead of 72 characters in segments E1EDPK2 and E1EDKP2 (ORDERS and ORDCHG).

Also refer to Notes 410989, 446008 and 446280.
6. After you change a purchase order or contract, no EDI message is output. Error ME760 is listed in the processing log of the message.

When processing changes, table T166C is checked and analyzed in the EDI environment, just as is the case in the print output. This information will only be issued if the changed field exists in table T166C. See also Notes 310004 and 512700.
7. Which user exits are available in purchasing for the IDoc output of purchase orders using ORDERS and ORDCHG?

You can use Transaction CMOD with SAP enhancement MM06E001 to find the user exits (you can also find them in the object navigator in the XM06 function group), for example, the following exits are relevant:

a) EXIT_SAPLEINM_012 -> Customer enhancement for configuration (table APPL)

b) EXIT_SAPLEINM_013 -> Customer enhancement for changing material configuration data

c) EXIT_SAPLEINM_001 -> Customer enhancements for enhancing the control record

d) EXIT_SAPLEINM_002 -> Customer enhancements for data segments

e) EXIT_SAPLEINM_011 -> Final customer enhancement

You can find an example of the programming of the exit 002 using Note 313925.

8. Are the components of a subcontracting item also output in ORDERS or ORDCHG?

You cannot output purchase order components in the ORDERS or ORDCHG IDoc.

9. Can I also create a purchase order with message category ORDERS?

You can only generate a purchase order from an ORDRSP message if you use the VMI Scenario (Vendor Managed Inventory). The distribution of purchase orders (ALE) using the message category ORDERS is not supported in the R/3 standard system. However, you can create purchase orders via the message categories PORDCR (as of SAP R/3 4.0B) and PORDCR01 (as of SAP R/3 4.70). For this purpose, read the FAQ Note 582221.

Order confirmations (ORDRSP)
10. The vendor sends a price change that can be accepted automatically. The IDoc is updated but the purchase order is not updated with the confirmed price.

Prerequisites for the use of the price update are:

a) Condition types EDI1 and EDI2 must be maintained in the condition schema.

b) The price transfer must be activated in the confirmation control key (Transaction OMGZ).

11. In the confirmation control key, you can set a tolerance of 99,99 % for the overrun or shortfall of the confirmed price. However, a higher tolerance should be accepted.

A larger tolerance in the confirmation control key is currently not possible for technical reasons. However, you can change these fields with the help of customer function EXIT_SAPLEINM_009 and then increase the fields accordingly.

12. The vendor sends an order acknowledgement and cancels one or several items of a purchase order (Rejection). The IDoc cannot be updated.

See Notes 66192 and 890812 for more information.

13. In the order acknowledgement, you want to accept every confirmed quantity, how can you do this?.

The quantity check occurs in subroutine QUANTITY_CHECK (Include LEINMF2E).For this, use the tolerance limits from the purchase order item for the GR/IR control (ME21/22/23) or the ‘Delivery’ tab page (ME21N), to calculate the maximum or minimum quantity. For maximum over delivery you can set the indicator in EKPO-UEBTK (maximum over delivery) in the purchase order.

If you confirm quantity = 0, you must consider the FAQ for “Rejection”. If you want the under delivery tolerance (EKPO-UNTTO) to be larger than 99.9%, you need to modify QUANTITY_CHECK.

14. You want to confirm partial deliveries with an ORDRSP message. Why does the system always issue error message ME794 here?

In the scenario of the order confirmation the inbound processing expects that the quantity transferred in message ORDERS is indeed transferred. If no quantity check should occur, refer to the question above.

15. With an ORDRSP message the system issues error message ME794.

Check if segment E1EDP20 exists in the incoming IDoc. This segment is necessary to receive the confirmed quantity. If the segment is not in the IDoc, the system calculates with quantity 0. If this covers the ‘Rejection’ case, refer to the questions on ‘Rejection’.

16. In an order acknowledgment, you confirm several items, and an error occurs for one item. Why does the system not update the other items?

Such a system response is not provided in the IDoc inbound processing. The IDoc is only updated if all data has been processed without errors (the all or nothing principle applies here).

17. In the definition of the confirmation control key in Customizing (OMGZ) for order acknowledgements (ORDRSP), the flag for the goods receipt assignment (T163G-WEZUO) has also been set. You receive confirmations for purchase orders via ORDRSP and you subsequently post the corresponding goods receipt. However, the vendor now sends a new confirmation for the same purchase order which overwrites the data in the confirmation overview. Why?

Due to technical reasons, defining an order acknowledgment with a goods receipt assignment is not supported. If the vendor sends a second confirmation, the system deletes the existing confirmation and replaces it with the new one, even if a goods receipt has already been posted. Read also Note 494377 on this issue.

18. Which customer functions are available in IDOC_INPUT_ORDRSP?

a) EXIT_SAPLEINM_018 -> Customer enhancement for changing the currency

b) EXIT_SAPLEINM_007 -> Import IDOC segment

c) EXIT_SAPLEINM_009 -> Customer enhancement for tolerance change

d) EXIT_SAPLEINM_014 -> Customer enhancement for price tolerances

e) EXIT_SAPLEINM_015 -> Customer enhancement for vendor material change

f) EXIT_SAPLEINM_005 -> Customer enhancement for order acknowledgment before posting

g) EXIT_SAPLEINM_008 -> Customer Enhancement for final activities

19. Which settings are necessary to ensure that prices are copied from the ORDRSP to the purchase order item?

Consider the attachment of this note. In the attachment, all steps for standard price schema RM0000 are documented.

20. You have defined your own different message types (for example, ZNEW and ZCHG) for messages ORDERS and ORDCHG. After the output of message ORDERS one or several items are provided with a deletion indicator in the purchase order. Why are these not transferred with the IDoc for message ORDCHG and why does this only occur with the first change message?

The program for the IDoc output of message ORDCHG uses the same logic as is used for printing purchase order changes. For the print output, the system only considers changes that have occurred since the time of the last correct message output with the same message type (for example, ZCHG). If you use a different message type for the change message, then this time is initial (no time interval can be determined). In this case the program response is as during the new printout but deleted items are not issued (it does not make sense to send the vendor a new purchase order with deleted items).

All of the subsequent change messages are issued correctly, because the program can determine a time interval between the existing message (for example, ZCHG) and the new message (for example, ZCHG) to evaluate the purchase order change documents.

Use the same message type (for example, ZORD) for the ORDERS and ORDCHG messages.

21. Can you also process EDI purchase order confirmations for scheduling agreements and contracts?

EDI confirmations with the ORDRSP message category are only possible for purchase orders.

For scheduling agreements, see Consulting Note 810340.

22. Is it possible to eliminate IDoc-segments in the outgoing purchase order (messages ORDERS, ORDCHG) by means of an IDoc view?

As of Release 4.6 it is possible to hide header and item texts in the IDoc with the help of an IDoc view (see also the release notes for Release 4.6A). Other purchase order data cannot be excluded from the IDoc output.

23. Is it possible to output IDoc conditions in the outgoing purchase order (messages ORDERS, ORDCHG)?

As of Release 4.6 it is possible to output header and item conditions. However, this is only possible if you use an IDoc view (see also the release notes for Release 4.6A).

Powered by ScribeFire.

I have a problem while getting the print preview of a consignment invoice in MR90. I have maintained the output type ZKON for consignment in MRM1. Then I have done the whole consignment process till MRKO. I have also posted MRKO successfully. But while taking the output in MR90, the system is saying that output cannot be displayed as some data is missing. Can you please guide me, where I am missing, since I also maintained the output conditions in the MRKO invoice document as well as in MRM1 transaction. Please guys, kindly help me.

Thanks and Regards,
Umakanth.
 
    
Reply 
 
hi,

sujit
 
 

Powered by ScribeFire.

Which invoice idoc I should use?   Posted: Jul 19, 2006 11:06 PM   Reply Vendor sends invoice after Goords recipts. When Invoice gets created and matched to the right PO I ned to generate Idoc outbound to the 3rd party system via XI. Iam confused witch Idoc I need to use? ACC_INVOICE_RECEIPT03(Accounting: Post Invoice Receipt) or INVOIC02 ( Invoice / Billing Document ) ? Please guide me

Ram Krish Posts: 262 Registered: 12/1/05 Forum Points: 4

Re: Which invoice idoc I should use?   Posted: Jul 20, 2006 1:18 AM   in response to: Ram Krish   Reply any experts?

Yusuf Lawal Posts: 12 Registered: 10/28/04 Forum Points: 0

Re: Which invoice idoc I should use?   Posted: Aug 23, 2006 4:42 PM   in response to: Ram Krish   Reply Hello Ram, my understanding is that INVOIC02 is a generic IDOC that can be used to post MM and FI based invoices. Configuration of your partner profile determines whether the invoice is posted to MM or FI. I’m not sure about the other IDOC ACC_INVOICE_RECEIPT03 but I will suggest you go with INVOIC02. Please award points if this helps.

Powered by ScribeFire.