Soul

You don’t have Soul,
You are Soul, You have a Body – CS Lewis

Categories: Uncategorized | Leave a comment

FU BAPI_INCOMINGINVOICE_CREATE

___________________________________________________
Short Text
Invoice Verification: Post Invoice

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

Categories: LIV | 2 Comments

SAP Germany: Photos taken by My Friend Jan Schmucker

Categories: SAP AG | 1 Comment

SAP Germany Office – Photos by my friend Jan Schmucker

Categories: Uncategorized | Leave a comment

OLD Release Strategy – Deletion

Deleting Old Release Strategy from the system
hi

U need to follow following sequence while deleteing release strategy

proceed as follows:
Make all the deleted release settings in Customizing again, save them, and then delete them in the following sequence:

1. Delete the release strategies

2. Delete the release indicators

3. Delete the release codes

4. Delete the release group

5. Delete the class (Transaction CL02), provided a new one was created for the new release strategies.

Then use Transaction SE16 to check if the entries in the tables T16FK, T16FV, T16FS, T16FC and T16FG, are deleted there may be entries from previous Customizing

(take help from basis for this Manually delete entries from table using %sap_edit Tcode after open the table with SE16N.)

If u have deleted in wrong sequence then reconfigure Release strategy and delete in above sequence

Deleting Old Release Strategy from the system
Pos
If you are on ECC 5.0 or above then

Use SE16N.

Enter the table T16FS.

Before executing type "&sap_edit" in the command window. The message "SAP editing function is activated" will appear.

Execute (F8).

The table will open as EDITABLE.

Select any line you want to delete and delete it.

Deleting Old Release Strategy from the system
Posted: Aug 13, 2008 7:33 AM in response to: Dspsac
Hi

Goto Transaction CL24N , Check for the Relase Class all the Strategy’s Present, if you can find the RS Which you think is deleted , Deactivate the Same By removing the Charcateristic values.

You can try to maintain this Table Directly VV_T16FS_2 -Release Strategies: External Purchasing Documents using SM30

T16FS is the Main table where all the Relase Strategies are stored.

got SE16N & check if the deleted RS exits or not.

Thanks & Regards

Deleting Old Release Strategy from the system
Posted: Aug 13, 2008 4:39 AM in response to: Dspsac
Hi

proceed as follows:

1. Delete the release strategies

2. Delete the release indicators

3. Delete the release codes

4. Delete the release group

5. Delete the class (Transaction CL02), provided a new one was created for the new release strategies.

Then use Transaction SE16 to check if the entries in the tables T16FK, T16FV, T16FS, T16FC and T16FG, are deleted there may be entries from previous Customizing

(take help from basis for this Manually delete entries from table using %sap_edit Tcode after open the table with SE16N.)

You should also read Note 350703.

OR

Instead of deleting just deactivate the older Rel str by removing the Charactertistics values in the classification tab of the Release strategy

Because if you delete the older Release strategy then this will create the inconsistencies in the Older Purchasing documents which is already affected by this release strategy.

So inorder to discontinue the older release strategy you just deactivate that by removing characterstics values. In future you will not find this release strategy in any of your newly created Purchasing documents.

Thanks & Regards,

Categories: Uncategorized | 1 Comment

Vendor Email

TABLES.

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.

Categories: Purchasing, Vendor | Leave a comment

Audio For WordPress

Categories: Uncategorized | Leave a comment

External Send – Sending PO by email

In order to send PO, your Basis team must configure the system first so that external email can be send out from SAP. If it is not configured, no settings you do on MM will work.

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.

Categories: PO Email | Leave a comment

PDF Creation

Exporting the Contents of Spool Requests
Use
You want to export the contents of a spool request in one of the following ways:

● 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.

Categories: PDF | Leave a comment

e.CATT

Categories: Uncategorized | Leave a comment

Blog at WordPress.com.