While creating SO with BOM material, plant is getting grayed out.

Hi,
I am trying to create a sales order with BOM material.
As soon as I give the material, sub items are getting added but I am not able to modify the plant for main item, fields such as plant, item category are gettinh grayed out.
Is this related to item category or any other setting,
Please help me.
Thanks,
Pramod.

Hi,
The field is getting greyed, because you created BOM for perticular plant and it's unique.
Second is about to item category, when explode bom in sales order then main item become HIGHER LEVEL ITEM,and all other are child or sub item,once it is at higher level it is in display mode,
Kapil

Similar Messages

While creating the project contract, contract line tab is grayed out

Hi Friends
We are implementing Oracle contracts and while creating the contract, contract line tab is grayed out. I can not inset the contract lines in it. Can you please help.
Regards
Dharam

I have generated the secure view again and issue got resolved.

Problem while Creating MVLOG with synonym in Oracle 9i:Is it an Oracle Bug?

Hi All,
I am facing a problem while Creating MVLOG with synonym in Oracle 9i but for 10G it is working fine. Is it an Oracle Bug? or i am missing something.
SQL> select * from v$version;
BANNER
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
CORE    10.2.0.1.0      Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL>
SQL> create table t ( name varchar2(20), id varchar2(1) primary key);
Table created.
SQL> create materialized view log on t;
Materialized view log created.
SQL> create public synonym syn_t for t;
Synonym created.
SQL> CREATE MATERIALIZED VIEW MV_t
2 REFRESH ON DEMAND
3 WITH PRIMARY KEY
4 AS
5 SELECT name,id
6 FROM syn_t;
Materialized view created.
SQL> CREATE MATERIALIZED VIEW LOG ON MV_t
2 WITH PRIMARY KEY
3   (name)
4    INCLUDING NEW VALUES;
Materialized view log created.
SQL> select * from v$version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
PL/SQL Release 9.2.0.6.0 - Production
CORE    9.2.0.6.0       Production
TNS for Solaris: Version 9.2.0.6.0 - Production
NLSRTL Version 9.2.0.6.0 - Production
SQL>
SQL> create table t ( name varchar2(20), id varchar2(1) primary key);
Table created.
SQL> create materialized view log on t;
Materialized view log created.
SQL> create public synonym syn_t for t;
Synonym created.
SQL> CREATE MATERIALIZED VIEW MV_t
REFRESH ON DEMAND
WITH PRIMARY KEY
AS
2    3    4    5 SELECT name,id
FROM syn_t;   6
Materialized view created.
SQL> CREATE MATERIALIZED VIEW LOG ON MV_t
WITH PRIMARY KEY
(name)
INCLUDING NEW VALUES; 2    3    4
CREATE MATERIALIZED VIEW LOG ON MV_t
ERROR at line 1:
ORA-12014: table 'MV_T' does not contain a primary key constraintRegards
Message was edited by:
Avinash Tripathi
null

Hi Nicloei,
Thanks for the reply. Actually i don't want any work around (Creating MVLOG on table rather than synonym is fine with me) . I just wanted to know it is actually an oracle bug or something else.
Regards
Avinash

MD04 issue with BOM Material

HI
We have a scenario where Sales order is Created with BOM Material. Sales order has been saved, delivered and Billed.
But still the BOM Material is shown in MD04, we tried running the Correction program SDRQCR21, but still the BOM Material shown in MD04.
Can anyone help on this issue.
Thanks

hi,
please check,
whether TECO has been done for production order from PP perspective.
after this the requriment from MD04 should disappear and finally refresh it.
you are requested to search the FORUM sir.
regarsds,
balajia

Check while creating PR with account assignment K

Hi Gurus,
Can I put a check while creating PRs for account assignment category K, that only statistical order number range is allowed.
In other words, user should not be allowed to put any internal order other than statistical order in PR, while creating it with account assignment category K..
Thanks in Advance,
Vikash

Hi,
You can check on business transaction RMBA - it's the purchase requisition. Set it to prerequisites and for the validation select the order type (it's better than a number range - I believe you use different order types for real/statistical I/O) from AUFK (you will see this structure as available, when creating a validation). If you do use the same order type, then check on I/O itself COBL-AUFNR.
Regards,
Eli

Problem while creating xml with cdata section

Hi,
I am facing problem while creating xml with cdata section in it. I am using Oracle 10.1.0.4.0 I am writing a stored procedure which accepts a set of input parameters and creates a xml document from them. The code snippet is as follows:
select xmlelement("DOCUMENTS",
xmlagg
(xmlelement
("DOCUMENT",
xmlforest
(m.document_name_txt as "DOCUMENT_NAME_TXT",
m.document_type_cd as "DOCUMENT_TYPE_CD",
'<![cdata[' || m.document_clob_data || ']]>' as "DOCUMENT_CLOB_DATA"
) from table(cast(msg_clob_data_arr as DOCUMENT_CLOB_TBL))m;
msg_clob_data_arr is an input parameter to procedure and DOCUMENT_CLOB_TBL is a pl/sql table of an object containing 3 attributes: first 2 being varchar2 and the 3rd one as CLOB. The xml document this query is generating is as follows:
<DOCUMENTS>
<DOCUMENT>
<DOCUMENT_NAME_TXT>TestName</DOCUMENT_NAME_TXT>
<DOCUMENT_TYPE_CD>BLOB</DOCUMENT_TYPE_CD>
<DOCUMENT_CLOB_DATA>
<![cdata[123456789012345678901234567890123456789012]]>
</DOCUMENT_CLOB_DATA>
</DOCUMENT>
</DOCUMENTS>
The problem is instead of <![cdata[....]]> xmlforest query is encoding everything to give < for cdata tag. How can I overcome this? Please help.

SQL> create or replace function XMLCDATA_10103 (elementName varchar2,
2                                             cdataValue varchar2)
3 return xmltype deterministic
4 as
5 begin
6     return xmltype('<' || elementName || '><![CDATA[' || cdataValue || ']]>
7 end;
8 /
Function created.
SQL> select xmlelement
2         (
3            "Row",
4            xmlcdata_10103('Junk','&<>!%$#&%*&$'),
5            xmlcdata_10103('Name',ENAME),
6            xmlelement("EMPID", EMPNO)
7         ).extract('/*')
8* from emp
SQL> /
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[SMITH]]></Name>
<EMPID>7369</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[ALLEN]]></Name>
<EMPID>7499</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[WARD]]></Name>
<EMPID>7521</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[JONES]]></Name>
<EMPID>7566</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[MARTIN]]></Name>
<EMPID>7654</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[BLAKE]]></Name>
<EMPID>7698</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[CLARK]]></Name>
<EMPID>7782</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[SCOTT]]></Name>
<EMPID>7788</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[KING]]></Name>
<EMPID>7839</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[TURNER]]></Name>
<EMPID>7844</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[ADAMS]]></Name>
<EMPID>7876</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[JAMES]]></Name>
<EMPID>7900</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[FORD]]></Name>
<EMPID>7902</EMPID>
</Row>
<Row>
<Junk><![CDATA[&<>!%$#&%*&$]]></Junk>
<Name><![CDATA[MILLER]]></Name>
<EMPID>7934</EMPID>
</Row>
14 rows selected.
SQL>

Net_PRICE problem while creating PO with BAPI_PO_CREATE1 ***ASAP

Dear All,
While creating PO with bapi BAPI_PO_CREATE1, The net price is not populating, though the logic is correct, as when i change the net price to some otrher value of in the bapi, while debugging, it is taking the Net price, but in general run, the price is over written by Gross price in PO, Please Help, Its Urgent.
Any Sample codes are welcomed, where Net_price is used.
Thanks in Advance..
Rewards Guaranteed.

Dear All,
While creating PO with bapi BAPI_PO_CREATE1, The net price is not populating, though the logic is correct, as when i change the net price to some otrher value of in the bapi, while debugging, it is taking the Net price, but in general run, the price is over written by Gross price in PO, Please Help, Its Urgent.
Any Sample codes are welcomed, where Net_price is used.
Thanks in Advance..
Rewards Guaranteed.

What is wrong with camera settings -can't get it out of X-ray view

What is wrong with camera settings -can't get it out of X-ray view

It sounds like you are using Photo Booth and not the actual camera app. If you are using Photo Booth - tap the little icon in the lower left corner of the app to return to all of the different effects. Or quit Photo Booth and launch the camera app.
To quit Photo Booth...
Tap the home button once. Then tap the home button twice and the recents tray will appear at the bottom of the screen. Tap and hold down on any app icon until it begins to wiggle. Tap the minus sign in the upper left corner of the app that you want to close. Tap the home button twice.

Error while creating sales order for material with another DIVISION

Hello Friends,
I have a problem with my sales order creation.
I have defined a new sales area 0010 / 10 / 01. I have the sales order type assigned to this sales area. (in VOV8 for the sales order type, in the 'General Control' the 'item division' is flagged.
Now, I have created the sold to party XYZ with all the partner functions defaulted same as the sold to party for the sales area 0010 / 10 / 01.
NOW, I have the material ABC with the DIVISION 10 in the basic data. I have extended the material to my sales org & dist. channel & plant.
Now, while creating the sales order for my sales area 0010 / 10 / 01 , I enter the sold to party XYZ - it is OK. But when I enter the material ABC, I get the error - "SHIP TO PARTY IS NOT DEFINED FOR SALES AREA 0010 / 10 / 10"
Please help to resolve the issue.
Edited by: Vivek on Aug 13, 2009 9:04 AM

Hi
Common division for Material Master data will not work
Because in the material master Division is a field not an organizational unit
Means when you create MMR you will give sales org, DC, Plant as organizational units and then enter but not division
Division is a field maintained in basic data and sales org data 1
This is the reason in t code you will find in t code VOR2 Common division only customer and conditions but not materials
But in t code VOR1 Common DC ,customer conditions and materials all there are available (you can check these t codes)
Coming to your issue Item div is clecked in your order type
This means the division in MMR has the priority or control for that order type
Your header division is 01 ( taken from customers sales area) and item division is 10 (taken from MMR as per your post)
So it differs
To process this order with Item div is clecked in your order type you need to extend your Sold to party ABC to the sales area 0010/10/10 (the sales area where the division of the material falls)
or alternatively
There should be a customer say DEF created in sales area 0010/10/10 who will be a ship to party ( your error is also the same)
for your ABC that is sold to party in sales area 0010/10/01 where the order is registered
Hope yopu are getting it
ABC in sales area 0010/10/01 will have or should have ship to paty DEF in sales area 0010/10/10
or
ABC should operate in in sales area 0010/10/10 too
If item division is not ticked then these are not necessary as the header division 01 will be valid for all items and syatem will not look MMR at all for division
Regards
Raja

Error while creating delivery with reference to STO

Hi,
I am getting the following error while creating the delivery with reference to STO
Document is incomplete: You cannot save the delivery
Diagnosis:
When the system checked whether saving delivery was
permitted, it determined that the requirements stored in
Define Incompletion Procedures for this document do not
allow this subsequent function.
I have checked the following already:
1. Maintained shipping data for both the supplying and receiving plants.
2. Shipping tab exists in the PO
3. Shipping point determination is checked.
4. Customer masters created for both supplying plants and receiving plant for the sales area created for STO
5. Material master is available in both receiving and supplying plants.
It is working fine in one client. and giving a problem only in the other.not able to figure out where the error is. appreciate your suggestions
regards
joe

Hi Joseph,
First go to transaction "VUA4" and see what is the incompletion procedure asigned to your delivery type. Then go to
"OVA2" and see what are the fileds maintained in incompletion procedure of the delivery type and the status groups assigned to them. Now you go to "OVA0(ZERO) and see whether the status group allows to save the delivery. If it doesn't you can untick that check box. But if this is a live system , i doubt if you would be bale to do that. Any way one of the possible causes is storgae location missing. Kindly pelase let me know If you need any more infromation on this.
Regards,
Ram Pedarla

Problem while creating IR with BAPI_INCOMINGINVOICE_CREATE

Hi,
Getting error message while creating IR through some external service. We are using the BAPI BAPI_INCOMINGINVOICE_CREATE to create IR.
Error Message is "There is different account assignment information in item 000001".
Could anyone let me know what exactly we need to pass for the field "Invoice Doc Item".
Regards,
Uma

Did you check the FM documentation? There are some illustrative examples given.
In case you do not have it:
here is an excerpt:
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 pieces of material A at $10/piece
Goods receipt: 10 pieces of material A
You receive an invoice against this purchase order, with reference to purchase order number 4500007491, order item 10, for a quantity of 10 pieces of material A and an amount of $116, including 16% sales tax. Enter the following data:
Table HeaderData
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
Table ItemData
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 pieces of material A at $10/piece
First goods receipt: 4 pieces of material A
Second goods receipt: 6 pieces of material A
You receive an invoice against this purchase order, with reference to purchase order number 4500007505, order item 10, goods receipt document 50010095, 2000, item 1. The invoice is for a quantity of 4 pieces of material A, a gross amount of $46.60 and 16% sales tax ($6.60). Enter the following data:
Table HeaderData
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
Table ItemData
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
Table TaxData
TAX_CODE (Sales 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 table HeaderData, which item data you need to enter in table ItemData, and which account assignment data you need to enter in table AccountingData in order to post an incoming invoice for a blanket purchase order.
You receive an invoice for the blanket PO 4500015172, PO item 10 for an amount 110 USD incl. sales tax at 10%. You want to distribute the invoice amount to the cost centers 1200 and 1500. Enter, for example, the following data:
Table HeaderData
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
Table ItemData
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
Table AccountingData
1st line: Change account assignment data
INVOICE_DOC_ITEM (Document item in invoice document): 0001
SERIAL_NO (Serial number for the acc. 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 a blanket purchase order, the following fields for quantities and units of measurement must not be filled in the tables ItemData and AccountingData:
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)
For more information, see the parameter documentation for tables HeaderData, ItemData, and AccountingData, or 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 pieces of material A at $1.00/piece
Goods receipt: 300 pieces of material A
This purchase order is subject to account assignment. You receive an invoice for it, refering to purchase order number 4500006846, order 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% sales tax. You want to change the planned account assignment for the second account assignment item and add an unplanned account assignment. Enter the following data:
Table HeaderData
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
Table ItemData
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
Table AccountingData
Row 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
Row 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
For more information, see the parameter documentation for tables HeaderData, ItemData, and TaxData, or Logistics Invoice Verification in the SAP Library.
Example: 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 pieces of material A at $1.00/piece
Goods receipt: 100 pieces of material A
You receive an invoice for this purchase order refering to purchase order number 4500006986, order item 10, for a quantity of 100 pieces of material A and $136.00, including 16% sales tax and $20.00 planned delivery costs. Enter the following data:
Table HeaderData
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
Table ItemData
Row 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 (Sales tax code): VN
ITEM_AMOUNT (Item amount): 100.00
QUANTITY (Quantity): 100
PO_UNIT (Unit of measure): PC
Row 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
Table TaxData
TAX_CODE (Sales 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 you what header data you can enter in table HeaderData, and what item data and withholding tax information you can enter in table TaxData in order to park an incoming invoice with withholding tax.
Purchase order: 10 pieces of material A at $10
Goods receipt: 10 pieces of material A
You receive an invoice for this delivery with reference to purchase order number 4500007505, PO item 10, GR document 50010095 2000, Item 1. The invoice is for a quantity of 10 pieces and a gross amount of $100. You have to pay 10% withholding tax for the gross amount. Enter the following data:
Table HeaderData
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
Table ItemData
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
Table WithTaxData
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 tables HeaderData, ItemData, and WithTaxData.
Example: Incoming Invoice with Amount Split
This example shows you what header data you need to enter in table HeaderData, what item data you enter in table ItemData, and what information you can enter in table VendorSplitData in order to create an invoice with an amount split.
Purchase order: 10 pieces of material A at $10
Goods receipt: 10 pieces of material A
You receive an invoice for this purchase order with reference to 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 distribute the gross amount to two vendor lines. 40% of the gross amount should be paid immediately by check, and 60% of the gross amount should be paid within 14 days, taking into account a 3% cash discount. Enter the following data:
Table HeaderData
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
Table ItemData
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
Table VendorItemSplitData
1st vendor 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 vendor 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:
Table HeaderData
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
Table ItemData
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
Table GlAccountData
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
Table MaterialData
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
For more information, see the parameter documentation for the tables HeaderData, ItemData, GlAccountData and MaterialData or 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 to enter in table HeaderData, which item data to enter in table ItemData, and which account assignment data to enter in table AccountingData in order to enter and post an incoming invoice.
You receive an invoice with reference to the 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 Euro incl. 16% tax. Service B has 812 Euro incl. 16% tax. Service A has an account assignment of 50% to both cost centers 1000 and 2000. Service B also has an 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:
Table HeaderData
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
Table ItemData
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
Table AccountingData
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
For more information, see the parameter documentation for the tables HeaderData, ItemData, and AccountingData, or see the SAP Library under Logistics Invoice Verification.
Example: Incoming Invoice for a 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 into table AddressData. If you do not enter data in table AddressData, the address data for the one-tine vendor are copied 1:1 from the purchase order into the invoice.
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 either overwritten or enhanced in 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 city 'Walldorf'. Enter the following data:
Table AddressData
ACC_1_TIME (Indicator one-time vendor): X
NAME (Name): SAP AG
POSTL_CODE (Postal code): 69190
CITY (City): 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 table AddressData.
Example: Incoming Invoice for a Different Payee
This example shows you which address data you must enter in table AddressData in order to enter and post an invoice for a different payee.
You receive an invoice for a different payee with name 'SAP AG', postal code '69190', city 'Walldorf', bank number '38070724' and account number '4711'.
Enter the following data:
Table AddressData
ACC_1_TIME (Indicator one-time vendor): ' '
NAME (Name): SAP AG
POSTL_CODE (Postal code): 69190
CITY (City): Walldorf
BANK_NO (Bank number): 38070724
BANK_ACCT (Bank account number): 4711

While Create PO alternate BOM Issue

HI All,
While Create PO Iam not able to find alternate BOM which have mainained 1 2 3 BOMs.
System is showing only 1 Deafule BOM Could please let me know how fix this issue.
Alt BOM is Universal -usage and alternate 1 2 and 3.
BR,
Nagaraj K

Hi Nagraj,
If several alternative BOMs exist, there is no possibility
of selecting the desired BOM interactively. Instead,
selection can be controlled via the following mechanisms:
- SELECTION BY QUANTITY:
A lot size interval for which the BOM is valid can be
entered in the BOM header.
A prerequisite is that the Selection method indicator is
not set in the material master record (MRP 4 view).
- SELECTION BY DATE:
Can be set in the IMG under Production -> Basic Data ->
Bill of Material -> Alternative Determination -> Define
Alternative Determination for Multiple BOMs (transaction
OS32). A prerequisite is that the Selection method
indicator the is set to 1 in the material master record
(MRP 4 view).
- SELECTION BY PRODUCTION VERSION:
Can be used if the same material has different BOMs with
different suppliers.
You create different production versions in the material
master record of the assembly (pushbutton in MRP 4 view)
and assign an alternative BOM to the versions on the
detail screen. You then enter the valid production
version in the info record in each case.
If NO selection mechanism has been defined and several
alternatives exist, the FIRST one found is pulled.

Getting error while creating PO for direct material in SRM 7.0

While creating PO in SRM for direct material,i am getting the error as :Backend error-No Funds center entered/derivedin item 00001(3000/2211100).Please suggest me the solution

Hi,
We are using PPS functionality with SRM 7.0
Regards,
Gopal
Edited by: gopalthadi on Feb 9, 2011 5:01 PM

Error while creating document with attachment.

Hi,
I am getting an error "An error occured while creating the original attribute for PDF"
I tried with out file attachment, it works as you know it is simple....
I tried with various types of attachments like .TXT and .WRD (changed both wsapplication and docfile parameters), however i get the same error. I tried both from presentation and application server (by providing   pf_ftp_dest                = 'SAPFTPA'    pf_http_dest               = 'SAPHTTPA' )
Any idea on how to solve this?
All i need is create a DMS document with a PDF attachment from application server. Are there any other ways to solve this issue?
ws_docdata-documenttype = 'ARE'.
ws_docdata-description = 'BAPI DMS'.
ws_docdata-statusextern = 'CR'.
ws_file-storagecategory = 'DMS_C1_ST'.
ws_file-wsapplication   = 'PDF'.
ws_file-description = 'Job output'.
ws_file-docfile = 'C:\CAD Integ BAPIS_46.pdf'.
append ws_file to it_files.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
     documentdata               = ws_docdata
IMPORTING
     return                     = v_ret
TABLES
     documentfiles              = it_files   .
BREAK-POINT.
IF v_ret-type CA 'EA'.
ROLLBACK WORK.
WRITE : v_Ret-message.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = '5'.
ENDIF.
Thanks
Pavan

Hi,
I found that it is due to document type = 'ARE'. I changed hte document type to one of hte standard type 'TST'. It works for presentation server, but does not work for application server. Any ideas? Any help is appreciated with points.
ws_docdata-documenttype = 'TST'.
ws_docdata-description = 'BAPI DMS'.
ws_docdata-statusextern = 'CT'.
ws_docdata-documentnumber = 'ZNG-10000000017'.
ws_file-storagecategory = 'DMS_C1_ST'.
ws_file-wsapplication   = 'PDF'.
ws_file-description = 'Job output'.
ws_file-docfile = p_file.
append ws_file to it_files.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
    documentdata               = ws_docdata
   pf_ftp_dest                = 'SAPFTPA'
   pf_http_dest               = 'SAPHTTPA'
IMPORTING
   documentnumber             = v_docnum
   documentpart               = v_docpart
   documentversion            = v_docver
   return                     = v_ret
TABLES
   documentfiles              = it_files   .
IF v_ret-type CA 'EA'.
ROLLBACK WORK.
WRITE : v_Ret-message.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = '5'.
ENDIF.
Thanks
Pavan

While creating po, the vendor material no should updated in PIR.

hi all,
i am facing one issue
the issue is, while creating po, we can search the material no according to vendor material no, but when we change the vendor material no in po item details in material tab and save the PO, that is updated in the PIR, if we tick the box(info update), that means the new no is update in PIR,
but suppose i entered the wrong no, so i want to edit that field again. but the new assigned no is not updating the PIR though i have checked the check box(info update)
that means, PIR is updating once but not second time. what is the possible solution.
regards,
susanta
Edited by: susanta bindhani on Jun 26, 2008 8:27 AM

hi pankaj,
read the issue perfectly,
supoose i have created PO, i have entered in the field of vendor material no-123, ok. and i tick the box(update PIR).
then i save the Po, i saw the change in PIR- 123
after i gone to change mode- me22n, thr, i again change the vendor material no to 456, ok, and i save the PO, then i saw it in PIR,
but no change. the field no is showing -123.
my question is why PIR is not updating second time only once.
pls give me some suggesion, my client need it urgantly.
regards,
susanta

While creating SO with BOM material, plant is getting grayed out.

Similar Messages

Maybe you are looking for