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
Similar Messages
-
Parts Requirement Create Order Error:Validation Failed for the field - Shipping Method DHL
Trying to create Parts Requirement.
Error message on clicking "Create Order" button: "Validation Failed for the field - Shipping Method DHL"
Please suggest the Setup that needs to be done for this.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 -
Order Import - Validation failed for the field - End Customer Location
I am trying to import an order using standard import program and it is failing with below error:
- Validation failed for the field - End Customer Location
I have checked metalink to debug this and found nothing, the values i have used to populate the interface table or valid.
Can someone please post your views on this, on where the problem might be.
Thanks!Hello,
Try the following
1) Check if any processing constraints are applied to customer/location
2) Try to create a new customer and associate internal location.
Create a new order to reproduce the issue
Thanks
-Arif -
Order Import Failed in OM : Log Validation failed for the field - Ship To
Problem in Order Management
When i tried to do Order import in Source Org logfiles shows the Message :Validation failed for the field - Ship To, Please if anyone have a solution of this.
Thanks in advance.
Regards,
Rajesh Verma
Senior Consultant- Oracle Apps.
COLTperhaps you might want to try populating customer_id instead of name to make sure that there is no error on typing customer name.
primary ship-to and bill-to must exist under this customer. During order import, if ship-to is not specified then import will fetch primary ST of customer.
This is what we use to populate interface table -with mininum of data.
INSERT INTO oe_headers_iface_all
(orig_sys_document_ref,order_source_id,org_id
,order_type_id,payment_term_id, shipping_method_code, freight_terms_code
,customer_po_number,salesrep_id
,sold_to_org_id, ship_to_org_id,invoice_to_org_id,sold_to_contact_id
,booked_flag
,created_by, creation_date, last_updated_by, last_update_date,last_update_login
,operation_code, order_category
,attribute5,tp_attribute4,xml_message_id,xml_transaction_type_code
,request_id, error_flag)
INSERT INTO oe_lines_iface_all
(order_source_id, orig_sys_document_ref, orig_sys_line_ref,orig_sys_shipment_ref
,inventory_item,item_type_code,line_type_id
,top_model_line_ref,link_to_line_ref,component_sequence_id,component_code,option_flag
,ordered_quantity
,order_quantity_uom,salesrep_id
,created_by, creation_date, last_updated_by, last_update_date,last_update_login
,operation_code,cust_model_serial_number,line_category_code
,context,attribute6
,reference_type, reference_line_id, reference_header_id
,return_context, return_attribute1, return_attribute2
,return_reason_code
,tp_attribute1,tp_attribute2,tp_attribute3,tp_attribute4,tp_attribute5
,request_id,error_flag) -
Validation failed for the field - Bill To Contact, Ship To Contact
Hi,
When I am trying to Import / enter order for a specific customer, i am getting the error.
VALIDATION FAILED FOR THE FIELD - BILL TO CONTACT
VALIDATION FAILED FOR THE FIELD - SHIP TO CONTACT
Has anyone got this error earlier? If you know the resolution, please update me on this.Hi,
I am getting following error when I an adding one customer address to another customer through Order Import Program. By populating 3 table values
1. OE_CUSTOMER_INFO_IFACE_ALL
2. OE_HEADERS_IFACE_ALL
3. OE_LINES_IFACE_ALL
Error Message:
Duplicate SHIP_TO ADDRESS found for IC_804810. Please correct the data.
Duplicate BILL_TO ADDRESS found for IC_804810. Please correct the data.
But its working fine when I am giving New address for existing customer.
Please help me on this....
Thanks,
Oracle Support. -
How to handle "Validation failed for the field - Tax code" issue?
We had mass uplaod the order that create on Mar with tax code effective date on Apr. Now we would like return on this order and getting error of "Validation failed for the field - Tax code". How to handle this issue?
Hi
You will have to check if the Tax_Code of RMA being received is the same as the one in the related sales order.
If not you will need to use the same tax_code.
Refer below document : Doc ID 1584338.1 -
Error " Data missing for the entry check while creating a new waste code
Hi all, While setting a new Waste code I get the error " Data missing for the entry check, correction:". while filling the NAM- WASTECOCAT - LER item.
This sould look for the catalog's name included in the phrase set but for some reason it doesn't find it giving me this error.
I am changing original Characteristics, phrase set, classes, and value assignment type. Just to have my own estructure with Znames for all of them.
I have also change the enviroment parameter "WAM_PHRSET_WACATLG" with the name of my phrase set.
I have checked everything several times watching for typos or looking for a missing step.
I have even tried including my new Z's characteristics in the classe and living the original SAP_EHS_1024_001_WASTE_CATALOG. (changing the enviroment parameter WAM_PHRSET_WACATLG to SAP_EHS_1024_001_WASTE_CATALOG) and it works.
I will like to change this characteristic by Z_EHS_WA_WASTE_CATALOG
Phrase set to Z_EHS_WA_WASTE_CATALOG.
enviroment parameter WAM_PHRSET_WACATLG= Z_EHS_WA_WASTE_CATALOG
After matching up the master data It should work fine but I might be missing something to get it running ok.
¿Any idea?
Regards,
AlvaroHello Juan Carlos, the value and class that I want to duplicate and doesn't work is for Waste Code, I have also duplicated the one you have displayed (waste pproperties) without any problem.
1.I have duplicated and changed class SAP_EHS_1024_001. to Z_EHS_WA
2. Create a copy of the 5 characteristics included in this class.
SAP_EHS_1024_001_WASTE_CATALOG
SAP_EHS_1024_001_WASTE_CODE
SAP_EHS_1024_001_WA_SUBCATEG
SAP_EHS_1024_001_WA_CATEGORY
SAP_EHS_1024_001_REMARK
change the name by
Z_EHS_WA_WASTE_CATALOG
Z_EHS_WA_WASTE_CODE
Z_EHS_WA_SUBCATEG
Z_EHS_WA_CATEGORY
Z_EHS_WA_REMARK.
I checked the funcion C14K_WASTECATLG_CHECK is in the value of the Z_EHS_WA_WASTE_CODE characteristic
I checked the funcion C14K_WASTECODE_CHECK is in the value of the Z_EHS_WA_WASTE_CATALOG characteristic
3. Create phrase sets for each new category. with same name.
4. Match up the master data.
5. Change the enviroment parameter.to Z_EHS_WA_WASTE_CATALOG
I think I have followed all the steps, but for some reason it doesn't find the catalog
The phrase for the catalog is EWC in english and LER in spanish.
Regards
Alvaro. -
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 -
User Exit for maintaining Checking Rule while creating Sales Order
Hi Gurus,
I have a requirement where I need to assign a particular value to Checking Rule (VA02 -> Display Availability Button -> Checking Rule field (beside Checking Group field)) while creating a Sales Order in SD (via. IDOC's).
In my requirement, within one Checking Group there are multiple checking rules assigned. When I am trying to assign the checking group in userexit_move_field_to_vbap (include MV45AFZZ), it is picking up the default checking rule ('A') and not the customized one defined for our requirement.
Is there any other user exit within which I can directly assign the Checking Group and Checking Rule while creating the sales order, please suggest.
Regards,
Arvind.You can use userexit 'USEREXIT_MOVE_FIELD_TO_VBAP' in include MV45AFZZ. This is executed every time a user changes anything on a material (e.g. put in a material number) and hits return. Just raise your pop-up window there if the user puts in the particular material you are talking about. The material number is available in xvbap-matnr.
Hope that helps,
Michael -
BOM not exploding for CR doc. type while creating sales order.
Hi Experts,
I have a problem in BOM. When created the BOM with sales doc. type OR, then BOM exploding as usual and picking pricing for main item.. But when I tried for sales doc. type CR, then the BOM is not being exploding and also pricing is also not picking. Can any one help me for this problem.
Thanks in advance,
Raksha.Hi,
Go to VTAF billing to sales document copy control and check below settings:
Header:
Data Transfer -052 Billing doc header
Data Transfer Buis - 103 Billing bus header data
Data Transfer Part - Billing Header Partner
Copying requirements - 021 Billing Header
Check Copy item number
Uncheck complete reference
Item:
Item Cat proposal G2N Request
Item TAN - Standard item
Data Transfer -153 item from Billing doc
Data Transfer Buis - 104 Billing bus Item data
Data Transfer Part - 004 Billing Item Partner
bl.pl - Leave it blank
Copying requirements - 303 Billing Header
uncheck copy schedule lines and do not copy batch
check update document flow
Pricing type - D
Leave blank - Campaign Deter.
Points to add: If you create without reference to an invoice then it would not explode BOM in RE return order because the configuration not set in REN item category.
As a standard business process return orders always create with reference to invoice.
regards
rc gopi -
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,
RenjithIf 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 -
End of Valid Logistic Calender error while creating Sales Order
Hi,
While creating Sales order in VA01 the following error message comes for particular material code for a particular site only:
24.01.2202 date comes after end of valid logistics calendar. (Please
correct)
Message no. 61062
Can anyone suggest on the same.
Regards
NiloferHi,
The input value given in Sales order is " Req Delivery date: 31.03.2012", but the error comes with the below date such as
"24.01.2202 date comes after end of valid logistics calendar.(Please correct)"
We also face one more error such as
" Incorrect index structure for table XMVERF_POS/0000224110/000040 ".
From where system is taking 24.01.2202 date? -
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 -
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 RoshanThank 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
while creating sales order for a particular plant there is error coming
NO NUMBER RANGE FOR DOC TYPE ZOS1VXBAK-AUARTSILD
PLANTXVBAK-VKBUR.
Intailly I have check the no series we have internal no series for all plant,the
number series which start 195000001, only one plant the giving the above error, rest all plant it is as applicable above series.
kindly guide me for the same.Hi Sanjay
This is regarding number ranges defining and assigning tips which you can follow as below:
Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for Sales Documents which are allowed for your New Sales Area.
Number Ranges can be maintained Internally by the system, however it can be maintained externally also if you customize it accordingly.
In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01.
Defining - The same can be reached through in IMG as : Sales & Distribution>Sales>Sales Document Header-->Define Number Ranges for Sales Documents.
Here you provide the system a specific Number range as follows:
Number range Key Start Number range End Number Range+Current Number
For Example: If you want to propose the following Number Range
*1 9000076000 9000076999 0
The Current Number field will be kept zero as you are proposing new number range and no sales documents have been created on it , Obviously..
*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should not be there in the system as existing.
If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in the system already, the system will throw a message that Interval already already exists. So choose a key that is unique, and which is not there in the system.
Here , by making this , you are assigning a Key to a Number Range Series.
All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order. For example: !1, ^A, BB,Z*,M2.........
Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have already proposed as above.
The Assigning Part is done as follows:
The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in V0V8.
This can also be reached in IMG by:
Sales & Distribution>Sales>Sales Document Header-->Define Sales Document Types
Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the Two Digit Number key in the Field- "Number range External Assignment"
Besides this:
If a new Shipping Point is created then Delivery Number ranges are required to be maintained.
Similarly,
If a new Plant is created then Billing Number Ranges are required to be maintained.
Regards
Naren
Maybe you are looking for
-
Hi, I noticed that there does not seem to be a way to edit data in a hierarchy viewer (Jdev 11.1.1.10). I even tried changing default <outputText> fields to <inputText> fields. I was wondering if someone had any suggestions. Thanks,
-
My mini keyboard for mac stopped writing
i can only write with keyboard viewer
-
Hello Friends, I am trying to setup a Price List ( in a new R12 instance, not a R12 VISION instance ). When with Responsibility "Oracle Pricing Manager", I click on Price List Setup, I get a message - Pricing APIs are not available for Basic Pricing
-
Using sub-directories in an email
Hi I want to attach an HTML file to an email using JavaMail. The HTML file contains links to image files that are stored in a sub directory (img). I am having problems representing the sub-directory structure in an Email created using JavaMail. Any h
-
Changing of the valuation type when the price is changed in Purchase ord
Hi friends we are using the batch management at material level. Now the batch is created on the following characteristics 1) Date of receipt of material 2) Date of production of material. Now the batch no and valuation type is coming same if we po