While creating sales order I am getting Sanctioned party list blocked but I am able to create delivery, and PGI

Dear GTS Experts,
While creating sales order I am getting Sanctioned party list blocked, but I am able to create delivery, and PGI.
Where Is the wrong ?
Thanks a lot
Venu gopal

Dear Venu
Based on your message shown in the system, can you check the field in Control Settings for System Reaction in the Document type settings via Application Levels in the feeder system. This Field '' System Response in Feeder system if SAP GTS fails'' should be maintained with ''A''. I think in your case it could be 'Blank'' Thats why the system is allowing you to create the subsequent documents accordingly.
Please let me know if any further inputs required.

Similar Messages

While creating sales order stock should not go under reserved block,

While creating sales order stock should not go under reserved block,
What is the customization?
Please help me.

Hi,
What exactly is your requirement?
Can you be a bit more detailed?
Thanks

While Savings Sales Order, I am getting error as

Plant 1000, not assigned to sales area
i chked in S0-DC for plant is OK, WHR S THE PROBLEM

Hi
In the customization assign the plant to Assign sales organization - distribution channel - plant
IMG>>>>>Enterprise Structure>>.Assignment>>>>>Sales and Distribution>>>>Assign sales organization - distribution channel - plant
regards

Error in confirmed quantity while creating sales order

Hi,
When I am creating sales order, I am getting confirmed quantity as 0. I have checked the following items,
1. Partial Delivery is permitted for the customer
2. Stock Ava liability is 1,100
3. Confirmed Issue I am getting 1,100
Please solve my problem why i am getting confirmed quantity as 0 and were i have to check for error
Please help me
regards,
PR Bhaskar Rao

Check what is there in the availability Check. Try to see the scope of check in the Scheduline tab of the sales order item. Also, check the date for which the item has been confirmed. You can also check what is the Requirement type that has come up.
You can also check in MMBE (for the plant, material and storage loc combination) if the quantity available is reserved for some other sales order and at the same time in the availability check you have made it to consider the reserved quantity..
All these will help you analyse why you are getting the confirmed quantity as 0.
Hope this helps...
Regards,
Mukund S

Error while creating sales order using SD_SALESDOCUMENT_CREATE

Hello All,
We are using to SD_SALESDOCUMENT_CREATE function module to create sales order it is working fine for single material.
When we try to create sales order with multiple matearials we ended up with the following errors
SALES_HEADER_IN has been processed successfully
000000
VBAKKOM
Internal error in communication between configuration and sales doc.CONFIGURATION_PROCESSING
000000
CONFIGURATION_PROCESSING
Error in SALES_ITEM_IN 000010
000000
VBAPKOM
Internal error in communication between configuration and sales doc.CONFIGURATION_PROCESSING
000000
CONFIGURATION_PROCESSING
Error in SALES_ITEM_IN 000020
000000
VBAPKOM
SALES_ITEM_IN has been processed successfully
000000
VBAPKOM
Could any one help me out to resolve this issue.
Thanks in advance....
Cheers,
Harsha

Hello,
Looking at BAPI errors. It looks like you are trying to create sales order with variant configuration.
Check Below SAP Note.
900380 - Configurable items in the SD process (idocs & bapis)
Regards,
Sameer

Creating Sales Order with credit card using Process Order API

Hi All,
When trying to create sales order with payment type as Credit card using Order data storing into staging tables and then calling Order Import Concurrent Program. The order is being created in ENTERED state.
While trying to passing the same details to Process Order API to create Sales Order, we are getting following error:
Unable to set up a Credit Card Bank Account for the Customer.
Credit Card information on the order is not valid.
Why getting this error while using Process Order API.
Regards,
KANN.

When using the API, are you trying to create the order as booked using the booked flag or the book action? I would recommend using the action if you are not. To troubleshoot, I would try the API without booking and then use the following article to determine the issue:
Unable To Setup A Credit Card Bank Account For The Customer. CC Information On The Order Is Not Valid (Doc ID 1450936.1)

Problem in creating Sales Order

Hi All,
We have 3 Document types ZS01,ZS02 and ZS03 for creating Sales Order. We have written one program to create Sales Order for document type 'ZS01'.
Our requirement is ,we should allow to create sales order of doc.type ZS01 thru that 'z' program only,we should not use ZS01 type to create sales order via VA01.So, we have restricted sales order creation using 'ZS01' thr' VA01 by authorisation profile.So in my 'z' program i couldn't call VA01 to create sales order.So I tried using BAPI,it is giving me the error "No maintenance authorization for document type ZS01".
Please guide or suggest me some alternative method to create sales order.
Thanks & Regards,
Sudipto.

Hi Sudipto,
There is no direct method of by passing a role, but u can try creating sales order thru FM BAPI_SALESORDER_CREATEFROMDAT2 with reference to a SO that is already created with ZSO1, or you might call the Z report program internally from ur program to create the SO.
Hope that helps
Anirban

While adding Sales Order

Hi,
I need to add sales orders through my add-on.
I could add the sales orders.
But, when I'm adding lines to the sales order, I'm getting the following issue:
"There is a difference between the document total and its components.[Sales Order - Rows-Warehouse Code ][line 0] [Message 439 - 133]"
This error occurs only for some of the sales order lines, others are getting added.
Please help me with this.
Regards
Mohana

For your information, I have the same problem and I do GetByKey a Sales Order set the DownPaymentAmount either I set it to DocTotal or any other amount I get the error
Edited by: Marc Roussel on Nov 10, 2010 3:02 PM
Edited by: Marc Roussel on Nov 10, 2010 3:03 PM

How to get pricing conditions while creating Sales Order

Hi Guys,
When we create sales order using VA01, price is automatically determined using pricing condition configured.
My requirement is, I need to know what would be the price of a particular item.Say i put one item A with quantity x,can I get which price conditions will be applied and what value will come for them.I need this because I need to validate this price with some other price put in a file .

I would suggest to use the Exit because that will be less efforts and you can implment and debug it easily. Moreover, you can restrict it by any condition e.g. order type, order reason because all the internal tables are available at that point.
Whereas, accessing the access sequence is cumbersome process. You need to go to all the combinations (tables) in the access sequcen and try to find out the suitable match .
Regards,
Naimesh Patel

Getting error in while changing sales order which is created using BAPI

Hi All,
   I have created the sales order using BAPI ( BAPI_SALESORDER_CREATEFROMDAT1 ) and i am successfully creating sales order using this BAPI. But while i want to change sales order iam changing Shipping Conditions in Header Data of sales order .its giving an error .can any know any thing about this.
Error mesage :    No status object is available for SDI 300082407/10    (Order Number/Item Number)
In Header i am passing these values ...
     wa_order_header_in-doc_type = vbak-auart.
    wa_order_header_in-sales_org = vbak-vkorg.
    wa_order_header_in-distr_chan = vbak-vtweg.
    wa_order_header_in-division = vbak-spart.
Do i required to pass the below values ? in Header structure ( BAPISDHEAD1 ).
REFOBJECTTYPE
REFOBJECTKEY
REFDOCTYPE
Regards,
Sudhakar Reddy A

rectified

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

Error while creating sales order with ref using SD_SALESDOCUMENT_CREATE

Hi
I am creating sales order with reference using function module SD_SALESDOCUMENT_CREATE , while creating i am getting error
Document doesn't have document category even thougth i am passing document category in header as well as item lavel.
In VBUK table there is no value for VGTYP.
Can you please help me how to resolve it.
Thanks & regards
kiran

Problem resolved by passing REFDOC_CAT in the FM along with SD_DOC_CAT.
Thanks

Error while creating sales order : Materail not listed !!!

Dear All,
While creating a Sales Order, I am getting this message. please let me know. what is listing means.
How to check it.
error message
Material XYYXY is not listed and therefore not allowed
Message no. V1118
Diagnosis
The material entered is not allowed for the transaction because the listing is missing.
Procedure
Check your entries. If they are correct, check whether the listing is complete.
end of errror message.
Thank You.
Regards
Venkat.
Will award points for useful replies.

Hi,
Hope this will make your fundamentals about listing clearer.
Material listing (and exclusion) lets you control which materials specific customers may (or may not) buy. For example, if you create a material listing for a specific customer, the customer can only order products from that list. You can also create a master record for material exclusion for a particular customer. Then the customer can not order excluded materials from you.
Material listing applies to two partner functions in Sales & Distribution: the sold-to party and the payer.
In the standard version of the SAP System, when the sold-to party and payer are different, the material listing check is as follows:
· If the sold-to party has a material listing, the system only checks this listing (no other check takes place).
If there is no listing for the sold-to party, but a listing has been created for the payer, the system automatically checks the payers listing.
· If no material listing data exists for either the sold-to party or payer, then the customer may order any material.
Regards
SD

Hi error while creating sales order

hi
i am getting 'not able to save' message while i am creating sales order.
how should i proceed to know where is the problem???
i tried debugging but it is taking lots of time, is there any other way i can know the reason for this error in standard code.
there is no wrong data entry while creating sales order.
i just want to know what are the ways to know where is the problem in the standard code.
thanx
rocky

hi ,
try too create a sales order after that check transaction code ST22 U WILL FIND AN SHORT DUMP then check in the source code extract an pointer will be visible where the error is coming and it will also show the program name , please read the dump analysis care fully
srinivas

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

While creating sales order I am getting Sanctioned party list blocked but I am able to create delivery, and PGI

Similar Messages

Maybe you are looking for