2LIS_11_VAKON missing newly created sales orders

Hi All,
Our Sales Order Condition - 2LIS_11_VAKON extractor is missing newly created SD's since 2 days and Sales Order Hearder & Item extractors brings correctly into BW.
Any inputs on this?

Hi Prasanna,
only the delta relevant fields of 2LIS_11_VAKON occurs a Delta in the Outbound Queue (LBWQ) and finally as a result in the Delta Queue (RSA7) for the relevant DataSource 2LIS_11_VAKON.
Please check the delta relevant fields in LBWE for the relevant DataSource. On the left side You see the Delta relevant fields, on the right side the possible fields which you can Append and make Delta relevant.
Is the LIS Job for Application 11 active to bring the Data from outbound Queue (LBWQ) to Delta Queue(RSA7)?
Please make a Delta test in ECC and change the relevant Field. After the change in LBWQ the Counter for Application 11 should increase by 1.
by the Way, in RSA3 you see only the Data from the Last Application Setup (e.g. OLI7BW for LIS11 DataSources), Delta records are only visible in RSA7 after the LIS Job (LBWE) was run.
hope it helps.
regards,
MIchael

Similar Messages

Freight Carrier missing while creating sales order using BAPI

Hi All,
I am using BAPI BAPI_SALESORDER_CREATEFROMDAT2 to create sales order. At header level, I am passing sold-to-party,ship-to-party and Freight Carrier fields as partners.
When the sales order is created it is creating partners sold-to-party,ship-to-party but freight carrier is missing in the partners.
To partners inernal table, I am passing the partner role and partner number as following:
      int_partners-PARTN_ROLE = 'AG'.
      int_partners-PARTN_NUMB = int_order-kunnr.
      append int_partners.
      clear int_partners.
        int_partners-PARTN_ROLE = 'FC'. "Frieght carrier
        int_partners-PARTN_NUMB = int_order-kunnr2.
        append int_partners.
        clear int_partners.
      int_partners-PARTN_ROLE = 'WE'.
      int_partners-PARTN_NUMB = int_order-kunnr1.
      int_partners-NAME       = int_order-name1.
      int_partners-NAME_2     = int_order-name2.
      int_partners-STREET     = int_order-street.
      int_partners-POSTL_CODE = int_order-post_code1.
      int_partners-COUNTRY    = int_order-country.
      int_partners-CITY       = int_order-city1.
      int_partners-REGION     = int_order-region.
      int_partners-TRANSPZONE = int_order-transpzone.
      int_partners-TAXJURCODE = int_order-taxcode.
      int_partners-district   = int_order-city2.
      append int_partners.
      clear int_partners.
Freight Carrier is set up as a "Vendor" instead of Customer in our system.
If anyone has solution to pass "Freight Carrier" through BAPI, please let me know.
Thanks,
Sonali.

For Vendor (Freight carrier) , I checked the master data and it has partner function defined as VN (vendor).
I have another issue with the salesorder create BAPI:
I am getting error
"E - 000010 : Condition rate does not agree with init. indicator for condition PR00"
when I am updating the PR00 condition value with '0.0' .
Please advice if anyone has any idea.
Thanks,
Sonali.
Thanks,
Sonali.

Bapi: create sales order with reference to Invoice.

HI ,
i am trying to create sales order(credit memo request) with respect to invoice.
What BAPI to use. also, please provide with sample code.
I have passed invoice to BAPI_SALESDOCU_CREATEFROMDATA1 at header level(ref_doc).
and i am passing other details correctly. the pricing procedure attched to original invoice is not getting triggered for th newly creating sales order.
Please help me with this.

use BAPI_SALESORDER_CREATEFROMDAT2
search the forum for sample program

Missing data: G/L Account----Create Sales Order

Hi all,
I am testing scenario for individual purchase order in sales. That is material type:HAWA Item category:TAB Schedule Line:CB.
The test is OK.
But when I create sales order for it , it pops up
Missing data: G/L Account
Message no. VU019
Diagnosis
The system checked the document for completion and found some missing data.
System Response
You cannot continue processing.
Procedure
Enter the missing data.
I have checked the log of incomplete items, no item for GL Account.
Could anyone please kindly give some suggestions?
Regards

Hi
check the below SDN links
[Re: Missing data: G/L Account :.Message no. VU019|Missing data: G/L Account :.Message no. VU019;
[Re: G/L Account missing|G/L Account missing after Upgradtion to ECC6.;
[Re: Error in Sales Order savings Missing data: G/L Account Message no. VU019 |Error in Sales Order savings Missing data: G/L Account Message no. VU019;
Regards,
Prasanna

Error while creating sales order with ref to contract

while creating sales order, with refernce to contract system is giving a message
Configuration not possible for material : Reason 3 --> Help
Message no. V1360
and the message is as follwed can any one explain
Diagnosis
This may have been caused by one of the following:
1. The configuration profile for the material allows or requires the bill of materials to be exploded during order processing. However, a plant has not been specified in the item.
2. The configuration profile of the material allows or requires the bill of materials to be exploded during order processing, but the order quantity in the item must be greater than 0.
3. A configuration profile has not been maintained
or
A configuration is not permitted for the material
or
4. The configuration profile of the material allows or requires the bill ofmaterials to be exploded during order processing. However, the system could not determine a date because important data is missing from the item (see incompletion log).

Hi
I think you have both Variant configuration and BOM.
Pls ensure the following.
1. BOM masterdata is maintained for the variants
2. Variant configuration is configured correctly
Configuration profile is created for the material
Knowledge base object and run time version are available
3. Maintain materials as not relevant for delivery or dont give delivery quantity as 0
Once you are sure that these are in proper shape, you can start creating order. The problem wont come.
Reward points if it helps you.

Error throwing while creating sales order

Dear all,
While on sales order creation,We have entered order type,sales organization,distribution channel,divison,
on entering sold to party,presssing enter,error is throwing as
No customer master record exists for sold-to party
actually customer master record is already created,
We need to extend the sales area then only system is allowing to create sales order,
Is there is any setting missing in configuration ?
Thanks
Jeyakanthan

hi,
can be done in two ways
1, only for the paticular customer
goto XD01 and extend the customer by entering new sales area above
and the already exisisting sales area in the reference
2,common distribution channel and common division(this is for all the customer created in that particular sales area)
IMG>sales and distribution>master data
regards
senya

Error: Validation failed for the field - Status While creating Sales Order

Hi,
I am getting an error while trying to create sales order header.
I have tried using provided in the metalink as well but it still doesn't seem to work.
I am on R12.1.1
Can somebody help me out on this?
The code is
set serveroutput on
DECLARE
l_header_rec OE_ORDER_PUB.Header_Rec_Type;
l_header_rec1 OE_ORDER_PUB.Header_Rec_Type;
l_line_tbl OE_ORDER_PUB.Line_Tbl_Type;
l_line_tbl1 OE_ORDER_PUB.Line_Tbl_Type;
l_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type;
l_header_adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
l_line_adj_tbl OE_ORDER_PUB.line_adj_tbl_Type;
l_header_scr_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
l_line_scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
l_request_rec OE_ORDER_PUB.Request_Rec_Type ;
l_return_status VARCHAR2(1000);
l_msg_count NUMBER;
l_msg_data VARCHAR2(1000);
p_api_version_number NUMBER :=1.0;
p_init_msg_list VARCHAR2(10) := FND_API.G_FALSE;
p_return_values VARCHAR2(10) := FND_API.G_FALSE;
p_action_commit VARCHAR2(10) := FND_API.G_FALSE;
x_return_status VARCHAR2(1);
x_msg_count NUMBER;
x_msg_data VARCHAR2(100);
p_header_rec OE_ORDER_PUB.Header_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_REC;
p_old_header_rec OE_ORDER_PUB.Header_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_REC;
p_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_VAL_REC;
p_old_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_VAL_REC;
p_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_TBL;
p_old_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_TBL;
p_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_VAL_TBL;
p_old_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_VAL_TBL;
p_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_PRICE_ATT_TBL;
p_old_Header_Price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_PRICE_ATT_TBL;
p_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ATT_TBL;
p_old_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ATT_TBL;
p_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL;
p_old_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL;
p_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_TBL;
p_old_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_TBL;
p_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL;
p_old_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL;
p_line_tbl OE_ORDER_PUB.Line_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_TBL;
p_old_line_tbl OE_ORDER_PUB.Line_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_TBL;
p_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_VAL_TBL;
p_old_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_VAL_TBL;
p_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_TBL;
p_old_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_TBL;
p_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_VAL_TBL;
p_old_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_VAL_TBL;
p_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_PRICE_ATT_TBL;
p_old_Line_Price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_PRICE_ATT_TBL;
p_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ATT_TBL;
p_old_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ATT_TBL;
p_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ASSOC_TBL;
p_old_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ASSOC_TBL;
p_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_TBL;
p_old_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_TBL;
p_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_VAL_TBL;
p_old_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_VAL_TBL;
p_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_TBL;
p_old_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_TBL;
p_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_VAL_TBL;
p_old_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_VAL_TBL;
p_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type := OE_ORDER_PUB.G_MISS_REQUEST_TBL;
x_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type;
x_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
x_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
x_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
x_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
x_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
x_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
x_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type;
x_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type;
x_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type;
x_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
x_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
x_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
x_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
x_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
x_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
x_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type;
x_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
x_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type;
X_DEBUG_FILE VARCHAR2(100);
l_line_tbl_index NUMBER;
l_msg_index_out NUMBER(10);
BEGIN
oe_debug_pub.debug_on;
DBMS_APPLICATION_INFO.set_client_info (121);
dbms_output.enable(1000000);
fnd_global.apps_initialize(2787,50703,660); -- pass in user_id, responsibility_id, and application_id
oe_msg_pub.initialize;
oe_debug_pub.initialize;
MO_GLOBAL.init('ONT');
X_DEBUG_FILE := OE_DEBUG_PUB.Set_Debug_Mode('FILE');
oe_debug_pub.SetDebugLevel(5); -- Use 5 for the most debuging output, I warn you its a lot of data
dbms_output.put_line('START OF NEW DEBUG');
--This is to CREATE an order header and an order line
--Create Header record
--Initialize header record to missing
l_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
l_header_rec.pricing_date := SYSDATE;
l_header_rec.sold_to_org_id := 2096;
l_header_rec.ordered_date := SYSDATE;
l_header_rec.sold_from_org_id := 121     ;
l_header_rec.salesrep_id := -3;
l_header_rec.order_type_id := 1003;
l_header_rec.operation := OE_GLOBALS.G_OPR_CREATE;
l_line_tbl_index :=1;
-- FIRST LINE RECORD
-- Initialize record to missing
l_line_tbl(l_line_tbl_index) := OE_ORDER_PUB.G_MISS_LINE_REC;
-- Line attributes
l_line_tbl(l_line_tbl_index).inventory_item_id := 124516;
l_line_tbl(l_line_tbl_index).ordered_quantity := 500;
l_line_tbl(l_line_tbl_index).ship_from_org_id := 563;
l_line_tbl(l_line_tbl_index).operation := OE_GLOBALS.G_OPR_CREATE;
-- CALL TO PROCESS ORDER Check the return status and then commit.
OE_ORDER_PUB.process_order (
p_api_version_number => 1.0
, p_init_msg_list => fnd_api.g_false
, p_return_values => fnd_api.g_false
, p_action_commit => fnd_api.g_false
, x_return_status => l_return_status
, x_msg_count => l_msg_count
, x_msg_data => l_msg_data
, p_header_rec => l_header_rec
, p_line_tbl => l_line_tbl
, p_action_request_tbl => l_action_request_tbl
   -- OUT PARAMETERS
, x_header_rec => l_header_rec1
, x_header_val_rec => x_header_val_rec
, x_Header_Adj_tbl => x_Header_Adj_tbl
, x_Header_Adj_val_tbl => x_Header_Adj_val_tbl
, x_Header_price_Att_tbl => x_Header_price_Att_tbl
, x_Header_Adj_Att_tbl => x_Header_Adj_Att_tbl
, x_Header_Adj_Assoc_tbl => x_Header_Adj_Assoc_tbl
, x_Header_Scredit_tbl => x_Header_Scredit_tbl
, x_Header_Scredit_val_tbl => x_Header_Scredit_val_tbl
, x_line_tbl => l_line_tbl1
, x_line_val_tbl => x_line_val_tbl
, x_Line_Adj_tbl => x_Line_Adj_tbl
, x_Line_Adj_val_tbl => x_Line_Adj_val_tbl
, x_Line_price_Att_tbl => x_Line_price_Att_tbl
, x_Line_Adj_Att_tbl => x_Line_Adj_Att_tbl
, x_Line_Adj_Assoc_tbl => x_Line_Adj_Assoc_tbl
, x_Line_Scredit_tbl => x_Line_Scredit_tbl
, x_Line_Scredit_val_tbl => x_Line_Scredit_val_tbl
, x_Lot_Serial_tbl => x_Lot_Serial_tbl
, x_Lot_Serial_val_tbl => x_Lot_Serial_val_tbl
, x_action_request_tbl => l_action_request_tbl
dbms_output.put_line('OM Debug file: ' ||oe_debug_pub.G_DIR||'/'||oe_debug_pub.G_FILE);
oe_debug_pub.debug_off;
-- Retrieve messages
FOR i IN 1 .. l_msg_count
LOOP
   Oe_Msg_Pub.get( p_msg_index => i
    , p_encoded => Fnd_Api.G_FALSE
    , p_data => l_msg_data
    , p_msg_index_out => l_msg_index_out);
   DBMS_OUTPUT.PUT_LINE('message is: ' || l_msg_data);
   DBMS_OUTPUT.PUT_LINE('message index is: ' || l_msg_index_out);
END LOOP;
-- Check the return status
IF l_return_status = FND_API.G_RET_STS_SUCCESS
THEN
dbms_output.put_line('Process Order Sucess');
dbms_output.put_line('new Header id:' || l_header_rec1.header_id);
ELSE
dbms_output.put_line('Failed');
END IF;
Commit;
END; Regards
knick

Kinck
The same script worked for me in vision (R12.1). You may have issues with your defaulting of a number of attributes that you are not passing in the API (like price list, line type and so on). You may want to check them.
Thanks
Nagamohan

Creating sales order document with reference to billing document

I have to create sales order with reference to existing billing document. I have tried to following bapis.
1. BAPI_SALESORDER_CREATEed
I have successfully created document with following details.
-->ORDER_HEADER_IN:
DOC_TYPE = ZRK
SALES_ORG = 3000
DISTR_CHAN = 00
DIVISION = 00
ORD_REASON = 100
SD_DOC_CAT = L
CURRENCY = EUR
REF_DOC = 100000028
REF_DOC_CA = M
-->ORDER_ITEMS_IN:
ITM_NUMBER = 000010
MATERIAL = 701791
TARGET_QTY = 0000000001000
CURRENCY = EUR
REF_DOC = 100000028
REF_DOC_CA = M
-->ORDER_PARTNERS:
PARTN_ROLE = SP
PARTN_NUMB = W12001
COUNTRY = NL
by providing this input i am able to create the document but it is not picking up the net value. so i have passed some extra paramters in ORDER_ITEMS_IN
COND_TYPE = PNET
COND_VALUE = 14,56
COND_D_UNT = PC.
folowing error is occured: Condition PNET is missing in pricing procedure A V Z0000.
is it something related to configuration problem?
2.BAPI_SALESORDER_CREATEFROMDAT1 or BAPI_SALESORDER_CREATEFROMDAT2
I have used same test data that is used for BAPI_SALESORDER_CREATEFROMDATA (where in i coudl succefully create doc). but here i encounterd following error.
Unpermitted combination of business object BUS2032 and sales doc. category L.
When i created manually using transaction : VA01
I could do the same by passing following inputs:
DOC_TYPE = ZRK
SALES_ORG = 3000
DISTR_CHAN = 00
DIVISION = 00
Reference document number.
Please suggest me right way of approach.

Hi,
In SAP, when the sub-sequent document is existing , we can not cancel the preceeding document. Therefore if you want to cancel the billing document you need to calcel the documents which are created with reference to that.
Check and confirm.
Regards,
Ravi Duggirala

Condition tab in display mode while creating sales order.

Hi Guys,
When I go to create a sales order the condition tab shows all the condition types in grey, irrrespective of its being manual or mandatory. I know it has nothing to do with V/06 or standard pricing transactions. So I changes the item categry.Again used the same order type, same customer , same material and same sales area. Once I change the item category to Zxxx, Condition tab becomes changeable. So I concluded that item category is the culprit. But the question is Which part of item category is influencing it ?
Please help.
Regards,

Hi Phani,
While creating sales order (VAO1), I go to item level and click on condition tab. I see all the things in this tab grayed. Nothing is changeable. I changed the item category, while the pricing procedure was same as the old one. Condition tab became changeable. So it has something to do with item category. But what is that one thing missing in my item category which is making condition tab grayed out..?
Regards,

Create Sales Order With Reference to Billing Document Using BAPI_SALESORDER

Hi,
How can i create a sales order With Reference to Billing Document Using BAPI_SALESORDER_CREATEFROMDAT2?
Thanks in advance,
Alejandro.

I have to create sales order with reference to existing billing document. I have tried to following bapis.
1. BAPI_SALESORDER_CREATEed
I have successfully created document with following details.
-->ORDER_HEADER_IN:
DOC_TYPE =                  ZRK
SALES_ORG =              3000
DISTR_CHAN   =            00
DIVISION =                    00
ORD_REASON =            100
SD_DOC_CAT   =          L
CURRENCY       =         EUR
REF_DOC          =         100000028
REF_DOC_CA    =         M
-->ORDER_ITEMS_IN:
ITM_NUMBER    =           000010
MATERIAL          =          701791
TARGET_QTY     =          0000000001000
CURRENCY        =          EUR
REF_DOC           =          100000028
REF_DOC_CA     =          M
-->ORDER_PARTNERS:
PARTN_ROLE      =          SP
PARTN_NUMB      =         W12001
COUNTRY             =         NL
by providing this input i am able to create the document but it is not picking up the net value. so i have passed some extra paramters in ORDER_ITEMS_IN
COND_TYPE          =        PNET
COND_VALUE        =        14,56
COND_D_UNT        =         PC.
folowing error is occured: Condition PNET is missing in pricing procedure A V Z0000.
is it something related to configuration problem?
2.BAPI_SALESORDER_CREATEFROMDAT1 or BAPI_SALESORDER_CREATEFROMDAT2
I have used same test data that is used for BAPI_SALESORDER_CREATEFROMDATA (where in i coudl succefully create doc). but here i encounterd following error.
Unpermitted combination of business object BUS2032 and sales doc. category L.

Issue in creating sales order using process_header API (web service)

Hi All,
I am trying to create sales order header using web service call to OE_ORDER_PUB.Process_header API.
When I pass the inputs and test the service,I get output with return_status='S'. But no record falls at the OE_ORDER_HEADER_ALL table.
I cant identify where the problem is.Is there any commit missing? Pls help me resolve this issue.
Thanks,
Vinoth

Hi All,
I am trying to create sales order header using web service call to OE_ORDER_PUB.Process_header API.
When I pass the inputs and test the service,I get output with return_status='S'. But no record falls at the OE_ORDER_HEADER_ALL table.
I cant identify where the problem is.Is there any commit missing? Pls help me resolve this issue.
Thanks,
Vinoth

Error in BAPI_SALESORDER_CREATEFROMDAT2 to create sales order

Hi all,
I'm trying to create a sales order using bapi_salesorder_createfromdat2. I have given the import parameters as per the documentation. But i'm getting the following error messages from the return parameter
number       message
233           SALES_HEADER_IN has been processed successfully
233           SALES_ITEM_IN has been processed succesfully
555          The sales document is not yet complete: Edit
311           Standard Order 73 has been saved
I gave the partner role (SP) and partner number in ORDERS_PARTNERS. But i din get any message regarding its processing.
Pls can anyone guide me to create sales order using this bapi.
Thanks & Regards,
Revathi.

Hi
     I Think there problem in passing data to function module some important data is missing
    run the functional in se37 and pass the data and see the result i have created sale order by passing the value below
header-doc_type = 'ZS4'.
    header-sales_org    = wa_temp1-vkorg.
    header-purch_no     = wa_temp1-bstnk.
    header-distr_chan   = wa_temp1-vtweg.
    header-division     = wa_temp1-spart.
    header-purch_no_s   = wa_temp1-bstnk.
    wa_partner-partn_role = 'AG'.
    wa_partner-partn_numb = wa_temp1-kunnr.
    APPEND wa_partner TO it_partner.
    wa_partner-partn_role = 'WE'.
    wa_partner-partn_numb = wa_temp1-kunnr.
    APPEND wa_partner TO it_partner.
    CLEAR: wa_partner.
      wa_item-material   = wa_temp2-matnr.
      wa_item-plant      = wa_temp2-werks.
      wa_item-req_qty    = wa_temp2-fkimg.
      wa_item-target_qty = wa_temp2-fkimg.
       APPEND wa_item TO it_item.
with regards
Nilesh

Problem while creating SALES ORDER (OR)

Hi All,
I am unable to create sales order (OR)
Error : Material is not defined for sales areaI have created MMR and CMR Properly.
Please help.
Thanks In Advance
Regards
Abhi

Hi Abhi,
I face similar issue as faced by you.
I went to additional data and changed the description and added the description in which I wanted it to be added but does not help. Am I missing the right place where to make the change?
I am pretty sure that it is a language issue.
I created a sales order, added a product, it worked fine.
Now, I copied this product to a new product, changed description and added it in same sales order it does not work.
Best Regards,
Neha

Problem while creating sales order

Hi
   We are facing a problem while creating a sales order in R/3. The sales order number is getting generated. But we are not able to view the same in the backend meaning it is not there in the database. Any inputs would be of help.
regs
Steve

Hi everybody,
I've got a problem with this too. I use the BAPI_SALESORDER_CREATEFROMDAT2 with BAPI_TRANSACTION_COMMIT and the webdynpro shows me the document number created in R3 with a Success message. But when I go to R3 and try to display the created sales order, it doesn't exists. So... Maybe I'm doing something wrong with the BAPI_TRANSACTION_COMMIT. ¿Can anybody help me with this?
The code I use is this:
When the user pushes the SAVE button in the WebDynpro, this code executes:
    //@@begin onActionSave(ServerEvent)
     wdThis.wdGetSOCreaCustController().executeBapi_Salesorder_Createfromdat2();
     wdThis.wdGetSOCreaCustController().executeBapi_Transaction_Commit();
    //@@end
In the custom Controller I've got the code for those executions:
public void executeBapi_Salesorder_Createfromdat2( )
    //@@begin executeBapi_Salesorder_Createfromdat2()
     try {
          wdContext.currentBapi_Salesorder_Createfromdat2Element().modelObject().execute();
     catch (Exception ex) {
          wdComponentAPI.getMessageManager().reportException(ex.getMessage(), false);
     wdContext.nodeOutput().invalidate();
    //@@end
public void executeBapi_Transaction_Commit( )
     try {
          wdContext.currentBapi_Transaction_CommitElement().modelObject().execute();
     catch (Exception ex) {
          wdComponentAPI.getMessageManager().reportException(ex.getMessage(), false);
     wdContext.nodeOutput().invalidate();
    //@@end
¿Is something wrong? ¿Is something missing?

Problem in Creating Sales Order From One DB to another DB

Hello All,
I am trying to create a Sales Order in another database from the current database based on the Purchase Order but while creating the sales order system is throwing an error " In "To Whse" enter valid values [ZAPp 0] "
My Code for Creating Sales Order in another DB are as follows :-
             '==== Connect To another SAP Company ====='
            '=====================================
            Dim oCompany_DB As New SAPbobsCOM.Company
            oCompany_DB.Server = "OSL_SERVER"
            oCompany_DB.LicenseServer = "OSL_SERVER"
            oCompany_DB.UseTrusted = False
            oCompany_DB.CompanyDB = Database_Name
            oCompany_DB.UserName = SAPUserName
            oCompany_DB.Password = SAPPassword
            oCompany_DB.DbUserName = DBUserName
            oCompany_DB.DbPassword = DBPassword
            oCompany_DB.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2005
            lRetCode = oCompany_DB.Connect()
            If lRetCode <> 0 Then
                oCompany_DB.GetLastError(lErrCode, sErrMsg)
                If (lErrCode <> -4006) Then
                    Class_InterCmp_Main.SBO_Application.MessageBox(sErrMsg)
                End If
            End If
'===== Creating the Sales Order ====='
'================================
Dim oOrder As SAPbobsCOM.Documents = oCompany_DB.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oOrders)
            Dim DocDueDate As String = oRecord.Fields.Item("DocDueDate").Value
            oOrder.DocDueDate = DocDueDate
            oOrder.CardCode = Customer
While Not oRecord.EoF
                Dim ItemCode As String = oRecord.Fields.Item("ItemCode").Value
                Dim WhsCode As String = oRecord.Fields.Item("WhsCode").Value
                Dim Quantity As Double = oRecord.Fields.Item("Quantity").Value
                Dim Price As Double = oRecord.Fields.Item("Price").Value
                Dim Discnt As Double = oRecord.Fields.Item("DiscPrcnt").Value
                Dim TaxCode As String = oRecord.Fields.Item("TaxCode").Value
                oOrder.Lines.ItemCode = ItemCode
                oOrder.Lines.WarehouseCode = WhsCode
                oOrder.Lines.Quantity = Quantity
                oOrder.Lines.Price = Price
                oOrder.Lines.DiscountPercent = Discnt
                oOrder.Lines.TaxCode = TaxCode
                oOrder.Lines.Add()
                oRecord.MoveNext()
            End While
            lRetCode = oOrder.Add
            '=== Check For Error if any ===='
            If lRetCode <> 0 Then
                oCompany_DB.GetLastError(lErrCode, sErrMsg)
                If (lErrCode <> -4006) Then
                    Class_InterCmp_Main.SBO_Application.MessageBox(sErrMsg)
                End If
            End If
            oCompany_DB.Disconnect()
When i execute the above code company gets connected but sales order not getting added in another company.
Thanks,
Amit

You can not do it the alternate way Kevin suggests, direct DB inserts are prohibited by SAP and can corrupt your DB, particularly because unlike what most people think, all SAP documents affect more than just their own tables (e.g. the numbering table, the history tables).
Are you getting any error message, or is it returning 0?
If it is returning 0, then check is the document actually going to the newly created database or maybe somehow going to old one.
If it isn't returning 0, what is the error code and message.
Edit:
Also I do see an error in your code. As it stands, you are adding an empty line to the end of every order. This can cause problems for SAP.
Dim counter As Integer = 0
If counter <> 0 Then 'Not equals 0, forum hides lt & gt symbols.
oOrder.Lines.Add()
End If
counter = counter + 1
oOrder.Lines.ItemCode = ItemCode
oOrder.Lines.WarehouseCode = WhsCode
oOrder.Lines.Quantity = Quantity
oOrder.Lines.Price = Price
oOrder.Lines.DiscountPercent = Discnt
oOrder.Lines.TaxCode = TaxCode
Edited by: njmog1 on May 9, 2011 10:14 AM

2LIS_11_VAKON missing newly created sales orders

Similar Messages

Maybe you are looking for