"Procurement Wizard" window opens for a particular warehouse while saving Sales Order

Hello All,
We have upgraded SAP B1 8.8 to SAP B1 9.0
My client is facing one of problem while saving Sales order using particular warehouse.
Actually client is having 4 warehouses (A,B,C,D) in which if they use one particular warehouse "A" for saving Sales order they are facing a issue. The scenario is here below:
1. Client selects all required details of sales order with along with particular warehouse "A".
2. On saving SO "Procurement Wizard" is automatically triggered even if procurement document field is unchecked in logistic tab of SO.
3. This is happening only for a particular warehouse "A". Whereas if I select other 3 warehouses (B,C,D) the system saves SO without trigerring "Procurement Wizard".
Client is using SAP B1 9.0 PL 08
We don't want this "Procurement Wizard" window to open for this. As we haven't selected any check box for "Procurement Wizard" so it should not open for a particular warehouse "A".
Do you think any issue with my warehouse or system settings? Please let me know.
Please refer screen shots.
Thanks in advance.

Hi Saurabh,
As per your Screen Shot, I think you have Add-on.
Please stop that Add-on and then check above Scenario.
Thanks
Regards::::
Atul Chakraborty

Similar Messages

How/ where to check output type while saving sales order for confirmation

Hi All,
Could you anyone pls let me know How/ where to check output type while saving sales order for confirmation.
Present scenario : when the Sales Order is created the Order confirmation is sent irrespective of credit block of the sales order.
Requirement : Order confirmation ZA00 sent to the partner only for those Sales orders which does not have credit block and ZCLE sent to the partner if the order has credit block.
Now i want to know where exactly to check the output types "ZA00" and 'ZCLE' based on the credit block to send the confirmation to partener.
Quick help highly appreciated......
Preetham

Hi Santosh,
Thanks for the info. But here in this case I have to send the confiramation based on credit limit check. If credit limit check exceeds "ZCLE' should go as confirmation else 'ZA00' should go as confirmation.
Where can we check the credit limit whether it exceeded or not. My doubt is whether it is config issue or do we need to write code user exit or routine to send the specific output type for confirmation.
Thanks & Regards,
Preetham

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

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

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

Is it possible to have a window open for my library and the Itunes store so that I can toggle between the two? I want to check my library before I purchase songs to make sure that I don't already own them.

Is it possible to have a window open for my Itunes Library and Itunes store at the same time so that I can toggle back and forth between the two. I want to check my library before I buy songs to make sure that I don't duplicate.
Thanks!

No.

Can you fix , the fact that If you leave the firefox update window open for a long period (say 20 minutes in the background), then close all other windowns, then choose to install, it uses this extra time to estimate the download?

Can you fix , the fact that If you leave the firefox UPDATE window open for a long period (say 20 minutes in the background), then close all other windows, then choose to download update, it uses this extra time to estimate the download? (Mine said, 12 Hours to start with, but took under 2 minutes!)
== This happened ==
Not sure how often
== When you install update to 3.6.4 (Possibly for every update?)

The download should happen in the background (before you get an update window). I wonder why that didn't happen for you...\
Did you manually check for updates?

Open qty errin Selection list For Ref Doc. screen while converting to order

Hi SAP Gurus,
For one of my materials, the open quantity is not updating in the Selection list For Ref Doc. screen while converting to sales order.
Can you please help me?
Thanks,
Ketan

Hi Senthilkumar,
I really appreciate for your kind Hint of SEL ID.
I created and assigned new 'Sel Priority' to the SEL ID same as for Routing.
Now while converting Planned order to Production order system is asking for Reference operation set as there is no such need of Routing as I already mentioned in previous post.
Regards,

Confirm / Fulfill Open Qty pulling in partial quantity in sales order

Hello all,
    The inventory for item AA is 83.5 case for batch 123A.   In the sales order i create, for item AA with Order Qty of 83 cases, it pull in from batch 123A, confirming 83 cases.   Next line item AA, i need another 1 case. It goes to another screen 'Availability Control' where i click the 'Fulfil Open Qty Using Batches'.
Sap pulled 0.5 from remaining batch 123A and confirmed 0.5 case. It also confirmed the other 0.5 case from a new batch 456B.    It is breaking the cases into half from another batch.
I DO NOT want to take in partial cases from any batch. Is there a way i can make the system read in whole cases all the way ?   Is this config issue or programming ? Any user-exit ? Is this relating to sales order ?
Pls share your thoughts and experiences you may have ?
Thank you.
Joyce
Edited by: Joyce Chan on Feb 24, 2009 3:59 PM

no replies

Duplication of Purchase Order while creating sales orders for a customer

when we try to create sales order for one customer it have to create by picking up the purchase order from the table linearly.
But the problem is that here when we are trying to create multiple sales orders the same purchase order is being picked.
for example..when we create sales order 1 the purchase order picked is PO1 and
for creation of sales order 2 the same purchase order PO1 is being picked up instead of PO2.
No idocs are being generated in this, even to check them..
How shall i resolve this...? Please help me out ASAP

Hi Kumar,
Thanks for the reply. But actually the problem is that this is related to some customized table in the project. When a EDI Batch job runs in the background then automatically the SO is created and the PO is being picked from the table(custom table) and then posted against the respective SO. we are not aware of that job which is triggering this to debug. Once if we can know that particular batch job or pgm or edi or idoc what ever it is then we can debug.
Do you have any idea how can we find that particular pgm/edi/idoc/job name which triggers this creation of SO?

Asking for purchasing reqistioner no. while making production order

dear all
asking for purchasing reqistioner no. while making production order.how do get rid of this reqisitioner no. option from production order.
regards
manish sharma

Hi,
Chcek the BOM copied to the order or the items that you are entering while creating the order, if item categories are N, purchse requisitions are automatically created and related info is queried from the user. Change item categories to L, stock items if external procurement is not relevant.

How to bring in the Open Sales Orders while performing Sales Order Conv

Hi,
Could you give some suggestions on the below:
How to bring in the Open Sales Orders while performing Sales Order Conversion in R12.
Thanks
Pravin

See http://ramugvs.wordpress.com/2011/08/27/how-to-stage-and-import-an-order-using-order-import-api-apps-wms-ebiz-11i-r12/
Sandeep Gandhi

User Exit to check whether chapter id for Material and Plant combination is maintained while creating sales order

Hello all,
my requirement is, system should give error message while creating sales order, if chapter ID is not maintained for a material and plant combination.
please suggest the user exit.

Hi
CASE 1 : All Plants are excisable.
In Material master , Foreign Trade data tab- mentioned Control code field mandatory. ( i.e nothing but Chapter ID)
CASE 2 : Few Plants are excisable
In the Case 2 you need to go for Enhancement
Program Name : MV45AFZB
User Exit: USEREXIT_CHECK_VBAP ( Item Level Check )
By using above user exit you write a logic with the help of ABAPer
Plant and Chapter ID combination table : J_1IMTCHID

FM for Updating Installation date in Contracts + sales orders Item level

Hi
Plesae give any FM for Updating Installation date in Contracts + sales orders Item level for contracts tab.
Thanks and Regards,
Vishnuvardhan....

Have used the billing transaction to set a Default Billing date at time of blling.

Tax classification screen for item level not appearing in sale order under Billing Doc tab

Hi Expert
while creating sale order Tax classification screen is not appearing for item level under Billing document tab.
Tax classification for customer and Material has already maintained. Tax classification screen is not appearing for USER but same time from our USER ID we can able to see that screen.
please help in above issue. is this related to Authorization issue or other thing need to check.
Regards
Pash@SD

Hi,
As per standard in Sales Order Document you will be able to see the Tax Classification fields in Billing Tab at Header level (for Customer Tax Classification) and at Item level for (Material tax Classification). The values from Customer M<aster is not populated at Header level as per standard but you can populate the value by using the Exit. Material tax classification populated from material master as you can see that at item level.
If for one User you are able to see and for other you are not able to see, kindly check first whether both are using same customer and material, and if yes, then check the User Exit.
Thanks and regards,
Amitesh Anand

"Procurement Wizard" window opens for a particular warehouse while saving Sales Order

Similar Messages

Maybe you are looking for