How to restrict the the oreder reason list while creating sales order

Hi gurus,
Can anyone suggest me
how to restrict the Order rerson list
while creating the sales order in VA01
Thanks & Regards
kalyan.

hi,
Try this exit:
Enhancement MMFAB001 User exit for generation of release order
Thanks,
AMS

Similar Messages

How to block the material qty to 1 while creating sales order (VA01)?

Hi All,
Scenario : We have 20 Materials each with 100 qty in Plant. In the sales order we should have all the 20 materials with qty one. The sales order should throw an error if the material qty is more than 1 and should not allow to create a sales order.
so is there any transaction code where we can block the entire material qty to 1 from the same plant while creating sales order?
Note: We should not set in MM01 "Minimum order qty". Assume we have 100 material in plant we can't set for each material one by one "minimum order qty".Instead of that is there any option to set the whole material qty to 1 as minimum while creating sales order?
Kindly guide me how to proceed.
Thanks,
Renjith

If you have access to idoc before calling the processing Function module, Adding header text segments E1EDKT1 and E1EDKT2 to the idoc will create the header text.
Regards
Sridhar

How to make ship to address fields mandatroy while creating sales order

Dear forum Members,
My client oraganizes trade shows and hence ship to address vries everytime when sales order is entered for the same sold to party.So one times ship to customer is used in the sales order and address is entered at sales order level. Please note that at master data level all address fields are suppressed for one time customer.Hence there is no question of going back to one time customer account group and making any field mandatory.
While changing address for ship to at order level, there are few fields which are mandatory, for example city is mandatory. I also want to make zip code and region as mandatory.where is this controlled?Please note that this is not account which controls this. i have already done lot of r&d on account group and transaction variants which are not controlling these fields at sales order level.

Hi Kanwal,
Only incompletion procedure will not suffice for your requirement.
You need to make the field mandatory wherein, if you dont enter, system will not allow you for enterin further fields. For this you should do the following:
Goto transaction SHD0, you will get a screen where you need to enter you Tcode "VA01"
Below you define a transaction variant (starting with Z).
On the next tab you have Screen Variant. Here you enter screen variant name, program name & screen number.
Then you click on create.
Its like as if you are doing some kind of recording. Finally you will reach to the screen where there are options available to make the field mandatory.
For your reference the program is SAPMV45A screen number is 4001.
Further screen are self explinatory.
Hope this should solve your requirement
Regards,
Dhananjay

How to restrict the order reason in Tcode Va01 while creating sales order

Hi Gurus,
My requirement is
while creating sales order in VA01
if order type is Zvol
than the list of order reasons has to be restricted.
Now 15 are coming from OVAU tcode
I need only 5 from these.
Thanks & Reagrds
kals.

Hi,
By doing the user exit in IW32 we achieved the requirement of restriction of maintenance order TECO functionality if any Service Entry sheet pending with reference of maintneance order.
regards
JKM

How to change the status of material while creating sales order via BDC

Hai.
In BDC while creating sales order( va01 posting ) it is stucking up in middle saying material is new. I.e Sales order (va01) is not getting created because of material status is new . I want to create sales order (va01) even material status is new.
pls give me out the solution. Points will be rewarded.
thanks & regards,
sami.

Hi,
If you drag the line item a little towards the right side, you will find a filed material entered. The one you see in the material filed on sales order over view screen is the one determined. You can as well double click and see the fields material entered and material determined.
Is there anything else you are expecting to see as part of analysis ?
Regards
Sadhu Kishore

How to manual maintain TAX condition value while creating sales order

Hi
I am creating one Tax condition suppose JLST without access sequence .
while creating sales order I am manually maintain the % value of TAX. suppose it is 1%
then I see It show some value in TAX .
save that sales order & creating delivery document for that but when I create Invoice its show error.
" Tax code in procedure CMTAXP is invalid ".
I know the configuration only for Tax condition with vk11 condition record .
BUT now I want to maintain TAX condition at the time of creating sales order.
so I remove the access sequence of that condition .
but It shows tax code error while billing.
My main question is that If i maintain condition record while creating sales order then how i can assign Tax code .
Can it is possible ?
if yes then How?
please help me.
thank you

Hi,
The "straight-forward" answer for Tax Code creation is contact the FI consultant. He shall help you, by creating Tax codes.
I have tested, with creating a tax cond type (copy of MWST) & manually entering values. I can create Sorder, Dlv and Bill but I cannot create an Accounting document. That is because of every line (amount) a Tax code is necessary.
I THINK, you can NOT have manually filled tax codes; access sequence is needed to get the tax value (%) and the Tax code from the condition record.
There is lot of material on the web to understand Tax classification, code etc. etc. See a useful link below -
http://www.sapgeek.net/2010/04/sd-determines-tax-code/
In short Tax code is a must and take the help of your FI consultant for the configuration of the same.
BTW - Tax code is already made created for MWST, therefore I suggested that you can use MWST. Furthermore, you can change the values corresponding to Tax codes in FTXP.
But if you are a beginner in these things, better take help.

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.

How to customize Category and Category items list while creating New Model

Hi,
what the most convenient way to customize the Category and Category items list while creating New Model?
This is standard:
Now, what we want to achieve, is to customize this menu, to:
1. Display in the Category window only f.e. two categories:
- EA Diagrams
- BPM Diagrams
2. In the EA Diagrams, we want to have f.e. four copies of City Planning diagram, each of them should have different elements available, f.e. in the first copy, only Architecture Areas shall be made available, in the second one Architecture Areas and Business Functions, in the third on f.e. only Business Functions shall be made available. Additionally, it should behave like a hierarchy ... meaning you can create the second diagram, only as child (related diagram) of the first diagram etc.
I know, excluding the particular diagrams/diagram elements can be configured using the right/profile settings, but how to:
1. Customize the standard New Model menu window
2. Create copies of City Planning Diagrams with different set-ups
3. Set the relationship between diagrams
Is such a configuration change possible?
Thanks a lot for your help!
Regards,
Rafal

Now, what we want to achieve, is to customize this menu, to:
Question #1. Display in the Category window only f.e. two categories:
- EA Diagrams
- BPM Diagrams
Click on Tools => General Options=> Model Creation
Click on Properties => at right of Default category set
Note : Model template does not work as Category. We can't set. An enchancement request has been open to SAP
In the following example I defined a new default (MyNewDefault.mcc). As you can see only BPMN models are available.
To create a new category set with BPMN choice
a) Copy default.mcc in MyNewDefault.mcc file.
    Go to Tools=>General Options=>Model Creation : Select your new category
    Go to Tools=>General Options=>Model Creation : Edit properties and remove all things you does not want keep
or
b) Go to Tools=>General options=>Model Creation : Edit properties and click on Save as button and specify the file name "MyNewDefault".
    Quit the window.
    Select you new category : Go to Tools=>General Options=>Model Creation : "MyNewDefault"
    Edit properties and remove all things you does not want keep.
    Save you new category
Question #2. How to define copies/replicas of existing diagrams
     Wrote an extension
Question #3. How to make sure, particular diagrams can be used (created) only on predefined "levels" and how to set the parent-child relationship, so that PD enforced it directly when creating a new diagram.
     Specify yours conditons in your extension attached to your model
     Example : When the user want create a child diagram : You can display a list of Parent Diagrams to select from.
     You can set in your extension by VBScript parent-child relationship
Question #4 In the EA Diagrams, we want to have f.e. four copies of City Planning diagram, each of them should have different elements available, f.e. in the first copy, only Architecture Areas shall be made available, in the second one Architecture Areas and Business Functions, in the third on f.e. only Business Functions shall be made available.
If I understand well your question. I suggest to take a look in
Repository=>Administration=>Objects Permission Profile
You can specify objects to show, mask, deactivate at model level.
You can specifiy your own metadata.
But I'm not sure you can mask, deactivate functions following diagram selection. It seem to specific.
Message was edited by: Benoit Le Nabec

How to set default reject reason in VA01 (create sales order)

Hi
Everybody can tell me how to set default reject reason for item in sales order.
in our sap system there are a default reject reason as '90'. We want to set it as "Null".
Thanks
Henry

Hi,
Assigning a default Reason for Rejection is not in standard SAP. I am sure there is some enhancement/user exit which updates the reason for rejection.
Please get the help of an ABAPer, create the sales order in debugging mode and he will find out the logic behind the automatic reason for rejection.
Before that you can find the exits in the include MV45AFZZ for any code related to this.
Hope this helps

How to save LIST_LINE_ID of Price List when create Sales Order Line

I dont know how save the LIST_LINE_ID of the Price List on Sales Order or anywhere when create Sales Order Line.
I create with the following steps:
Step 1: Create Price List for Item A with two line: Line 1 (Unit Price = 10,5, Pricing Attribute with Tax Classification Code = 5%), Line 2 (Unit Price = 11, Pricing Attribute with Tax Classification Code = 10%)
Step 2: I create Sales Order Line with Item A, Tax Classification Code = 5% --> Unit Selling Price = List Price = 10,5 but dont bookorder
Step 3: I update the Unit Price of Line 1 into 11.55.
Step4 : I book this Sales Order. Howerver, I use form personalization to customize Book Event: if the Unit Price of Item on Price List > Unit Selling Price then cant not Book. But I dont konw List Price of Sales Order belong the line of Price List.
Please help me check this issue. Thanks for your supports.
BinhTC
Email: [email protected]

Bob's right - except that if you have OM: List Price Override Privilege set to 'Unlimited' (and from your scenario it sounds as if you have) it is possible that the value in unit_list_price will vary from what was originally retrieved from the price list.
In that case, a safer bet is to use :LINE.original_list_price in your personalization as this will always contain what was originally retrieved and will mean you can avoid any repeat lookup via list_line_id.
Regards,
Jon

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

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

How to avoid XVBPA line item values while creating sales order

Hi Friends
I am creating Sales order using function module IDOC_INPUT_ORDERS, for that I am passing partner details through segment E1EDKA1.If I pass the same partner details(Partner number, name1,name4,city,postel code) which is same like customer master,
I can able to book the order and entries are coming only one time in VBPA table(Header Item level).But if I change any value for the particular partner in the Input(For example Name4, there is no value in customer master but I added through program).Now its creating an order but its showing the entered partner informations in header level.When I checked the same in line item level, its not picking the values from header, its picking the values from customer master for that particular partner.
So this line item also coming in VBPA table, because its different from header data.
Anyone guide me, how to avoid this problem while booking order through program.
Thanks
Gowrishankar

I am updating Ship-To-Party value in segment E1EDKA1 and calling IDOC_INPUT_ORDERS function module to create the sales order.
In this case for the particular partner there is no NAME4 value in KNA1, I am passing some value through this segment E1EDKA1.
So its creating an order with this new addresses , so its generating new ADRNR in VBPA header level.Thats fine.But the same time
its not copying the same value from header to line item.
In Line item level again its picking the address details from KNA1 for the particular partner number.So its showing Blank value in NAME4 field of line items.Its creating and spllitting issue, while creating delivery.
Thanks
Gowrishankar

How to restrict users to not default layout while creating a user specific?

Hi all,
I have a problem with frequent changes in report layout setting. When users trying to create a user specific layout in the window "Default" is set, out of "User specific" & "default" checkbox defaultly, so users saving the layouts. so it's overwritting on existing layout. we are ossing the old data. how to restrict end users to create new one with out changing the existing one.How to change that default check in "Default" check box to user specific defaultly. where i have to do settings for this. Thanks in advance.
Pradeesh

Hi ,
My problem is still not resolved. I tried applying the people picker property and set a specific field(an email id field) to be available to only admins. Now the field is not visible to the normal users but only admins which is good but that email field
should be able to take normal users as wel as admin's email ID. currently due to the people picker property it only takes admin's ID and not normal user's ID - which is not as per expectation.
What this email ID field does is - when a normal user is logged in he/she wont see this field in that view. But when an admin logs in he/she can switch to admin view and see this field . The admin can put any user's ID in this field and pull out the required
resource's Time Report for modification.
Please let me know how do i overcome my problem. Detailed step description will be very helpfull .
As per Cameron's suggestion (add a rule on the "additional admin section") , i am not sure how exactly that is done. Would help a lot if i got to know how this works.
Regards,
Guru

Facing the problem while creating sales order

Hi,
I am facing the problem while saving the sales order.
Error in system xxx/400 while copying the document
Message no. CRM_ORDER_MISC 020
Diagnosis
Errors occurred while transferring the document into another system. To view the error messages, see the enclosed log.
Transmission log
u2022Product cannot be recoded for ERP System xxx/400(Notification E CRM_ORDER_MISC 015)
u2022Product cannot be recoded for ERP System xxx/400 (Notification E CRM_ORDER_MISC 015)
Kindly assist me.
Madhu

Hi Madhusadan,
Can you check whether the product exists in the ERP System or not? You can take the product names and can check the same using the Tcode: MM03 in ECC System. Also, it would be good if you have a look at the product from the CRM System if there are any errors or the product is already archived.
Is the Sales Order you are creating from a Preceding Transaction ?
Hope this helps.
Thanks,
Samantak.

How to restrict the the oreder reason list while creating sales order

Similar Messages

Maybe you are looking for