Blocked field in Sales Order when using configurable materials

Hi everyone,
I have noticed that every time I insert a configurable material in a Sales Order Line, after pressing ENTER and having valuated the associated characteristics, the Material and Position Type fields stay blocked so I cannot change the material in this position.
According to the process I am implementing, I would need in certain cases to change the material (replacing the configurable for a non-configurable one).
I would be very grateful if someone could help me to avoid that these fields get blocked or at least to know the reason.
Thanks in advance and best regards.
Ben.

I don't have any experience with configurable materials, but it seems that in this case you'll need to delete the line (or the lines) and re-enter them with the proper type of material.

Similar Messages

Why pop up is shown to ask for inputing sales order when using COR1

I want to create a process order with order type PI01, but pop up window is shown to ask for sales order when using COR1. I suppose there is something wrong with material master setting, but I've never set classification to this material.
Please help.

Hi Nichole
Is the material assigned to any MRP group , if yes then check the config settings on t-code OPPR, if stg group is assigned. also check the matrial type to default MRP group assignment settings in SPRO>production>mrp>MRPgroup> Define MRP Group for Each Material Type.
regards
Prasad
reward if useful

Populating Customized fields in Sales Order Creation using BAPI

Hi All,
I have a requirement that, I need to populate 2 customized fields which are appedned in the VBAK tables through Append structure. I am using BAPI_SALESORDER_CREATEFROMDAT2 FM for creating it.
Could anybody tell me how to send these 2 coustomized field values in this BAPI using EXTERNIN parameter.
Regards
Rajesh
[email protected]

Hi,
To add data to custom fields there are two appraoches.
1)Using the EXTENSIONIN in the Tables option in the FM BAPI_SALESORDER_CREATEFROMDAT2
Check the Documentation for the same,
Customer Enhancement for VBAK, VBAP, VBEP
Description
You can use this parameter to transfer user-specific enhancments to a BAPI. The customer has to complete the EXTENSION structure and the system automatically continues processing it. If you have not defined any user-specific fields, then you can transfer a blank EXTENSIONIN structure.
Technical information about Customer Enhancements
The following description uses an example to explain how to proceed with customer enhancements to the SD tables VBAK, VBKD, VBAP and VBEP.
The customer has added their own fields to table VBAP using the INCLUDE structure CUTEST. This structure contains 2 fields:
CFIELD1, CHAR 10
CFIELD2, CHAR 3.
The customer also requires that these two fields can be maintained with the BAPI.
1. Maintain structure CUTEST in table VBAP
2. Because the BAPIs work with checkboxes, you must also define a CUTESTX checkbox for the customer structure. It should be structured like this:
Field name Data element
CFIELD1 CHAR1
CFIELD2 CHAR1
3. Define these customer structures in the structures VBAPKOZ und VBAPKOZX using INCLUDE or APPEND.
4. Add the customer structures to the BAPE_VBAP and BAPE_VBAPX BAPI structures using the APPEND technique.
5. Adjust the following structures for customer enhancements to table VBAK:
a) VBAKKOZ
b) VBAKKOZX
c) BAPE_VBAK
d) BAPE_VBAKX
6. Adjust the following structures for customer enhancements to table VBEK:
a) VBEPKOZ
b) VBEPKOZX
c) BAPE_VBEP
d) BAPE_VBEPX
7. Generally, the data should be added to the BAPI interface in the internal communication structures (VBAKKOM, and so on). There, you can process the data in the SD tables (VBAK, and so on).
8. If the EXTENSIONIN parameter contains customer data, you must complete at least the key fields in the relevant standard parameters.
For example:
You want to change customer field VBAP-CFIELD2 for item 20 to "XYZ" in order 4711.
The following entries are expected:
Import: BAPIVBELN-VBELN = '0000004711' Document number
 BAPISDHD1X-UPDATEFLAG = 'U' UPDKZ for doc header
Tables: BAPISDITM-ITM_NUMBER = '000020' Item number
 BAPISDITMX-ITM_NUMBER = '000020' Item number
 + BAPISDITMX-UPDATEFLAG = 'U' UPDKZ for item
You must complete the EXTENSION table as follows:
STRUCTURE VALUEPART1 1234561234567890123
BAPE_VBAP 0000004711000020 XYZ
BAPE_VBAPX 0000004711000020 X
Further Information
You can find more information in the BAPI programming guide in the chapter for enhancements to BAPIs.
Notes
You must complete the STRUCTURE field with the name of the relevant enhancement structure (BAPE_VBAK, BAPE_VBAP, BAPE_VBEP). You can complete the remaining fields with the append structures from the enhancement structures.
At the moment, you can use the BAPI to store enhancements in the following structures:
VBAK : An enhancement to header data requires an append structure to BAPE_VBAK and an enhancement to structure VBAKKOZ.
VBAP : An enhancement to item data requires an append structure to BAPE_VBAP and an enhancment to structure VBAPKOZ.
VBEP : An enhancement to schedule line data requires an append structure to BAPE_VBEP and an enhancement to structure VBEPKOZ.
VBKD : If you are using an enhancement for header data, you must add an append structure to BAPE_VBAK. You also need to enhance structure VBAKKOZ. If it is for item data, you need to add an append structure to BAPE_VBAP. You must also enhance structure VBAPKOZ.
If you also want to work with checkboxes, each X-structure must also contain an append structure.
For example:
A customer has created an order and wants to include the material long text (50 digits long).
The EXTENSIONIN structure must be completed with BAPE_VBAP. Two fields have fixed definitions in this structure. These are in the VBAP host key (VBELN, POSNR). The customer sets up an append structure that contains field ZMAT50.
Because the VBELN is normally blank when you create an order, the data can look like this:
STRUCTURE |BAPE_VBAP
2) Create the Sales Document using the FM and when successfully craeted you will get the Sales Document No in the Export parameter SALESDOCUMENT.
After its created and Committed using BAPI_TRANSACTION_COMMIT , do a BDC recording for the same to (VA02 Change Sales Order) update the fields only and save the document.
Regards,
AS

Sales Order User Exits - configurable materials !?

I have been tasked with investigating the following issue and if it can be solved via ABAP/User Exits. Users in an already live system are entering Sales Orders ( VA01 )with multiple Configurable Material line items and have to repeatedly enter the same characteristic values in each line item ( by entering Item Details >> Configuration ). They want to enter a set of characteristic values in the first line item and then have them defaulted into any further items. I have looked at the standard user exits in particular USEREXIT_MOVE_WORKAREA_TO_SDWA. Has anybody attempted anything similar to this !? Any ideas ?
Possible issues are:
1. How do I find the characterictic values from the 1st line item. ie. they haven't been saved yet, are they in a temp area similar to XVBAP for normal sales order line items !?
2. Are there are any suitable user exits in the Configuration side of things ( Function Group CEI0 !? ) to effect any changes the defaults. There are some BADIs in the code but they are not yet in use !?

Hi Jonathan!
I had a different requirement with sales orders and configuration, but this forced me into long debugging of behavior of all these exits.
1) Characteristics can't be read.
ad 1) in configuration it's possible to call function modules. Here (inside the configuration) values of characteristics are available and can be saved in global data of a Z-function module. This is later (in same transaction) available (like import/export).
2) I would propose to use functions of characteristics (as mentioned, it's possible to execute own function modules in configuration). It's possible to default values (meaning: output of your function is only done, if characteristic is not set) based on global data of Z-function module.
As long as a global memory is used, no interaction with other transactions has to be feared.
You don't need user exits (but a lot of coding).
You need to change the customizing of configuration - probably a huge task, because I guess you have a huge configuration (otherwise users wouldn't ask for maintenance help).
Regards,
Christian

BAPI for Creating Sales Order For Variant Configuration Materials

Dear Gurus,
Before posting this thread, we have referred many SDN threads, OSS notes and other sites for any sort of help..but no success..All threads and other referrals are not much of help as they are kind of incomplete( Perhaps, we are unable to understand them..no offense).
Few checked threads on this subjects are:
http://scn.sap.com/thread/34590
http://scn.sap.com/thread/851070
http://scn.sap.com/community/abap/blog/2014/04/23/update-vc-variant-configuration-data-using-standard-bapi-in-sales-order
http://scn.sap.com/community/abap/blog/2014/07/15/creating-orders-with-variant-configured-items-using-bapisalesordercreatefromdat2
http://scn.sap.com/community/abap/blog/2014/04/23/update-vc-variant-configuration-data-using-standard-bapi-in-sales-order
http://scn.sap.com/thread/120144
OSS: 549563
Well, we're using the BAPI (BAPI_SALESORDER_CREATEFROMDAT2) which creates the sales order successfully but without the characteristic values in line items.
We're passing data to the following parameters - ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_VALUE to create the variant config but not able to see it getting created.
Pls find attached BAPI coding document for your reference.
If you could throw any light on this issue will be of great help for us.
Thank You in Advance!!!
Reg,
Jagan-SD.

Jagan nath
Try below.
you would need miimum of 3 segments to pass variant config data using this bapi
ORDER_CFGS_REF for each configurable item
POSEX = ITEM #
CONFIG_id , root_id - Start with 1 and increment it for each configurable line item
ORDER_CFGS_INST
CONFIG_ID - from above
INST_ID - Start with 1 and increment it for each configurable line item
OBJ_TYPE = "MARA'
CLASS_TYPE = '300'
OBJ_KEY = material #
ORDER_CFGS_VALUE
CONFIG_ID for the item, INST_ID for the item
charc for characteristic value
VALUE for characteristic value
Reference thread
How to Fill Configuration Data in BAPI BAPI_SALESORDER_CREATEFROMDAT2
Hope it will solve your issue.
Thanks
Ritesh

Valuated sales order stock for configured material

Hi All!
I have a small problem : I created a new type of material (OMS2) - a configurable one, managed on quantity and value basis. I work with valuated sales order stock for configurable materials but the account in the purchase requisition is determined by means of event key GBB insted of event key BSX.
Where is my error?
Any idea would be appreciated.
Florina C

Hi
I think you are talking about Special Stock "E"...ie) Sale Order Stock...
If my understanding is correct then,
If you go and see the Table T156....For the
Movement Type: 101,
Special stock Indicator : E,
Qty. Updation Checked,
Val. Updation Checked,
Movement Indicator : Against PO,
Consumption Indicator: Sales Order Stock.....combination....the transaction Event Key....GBB only has been Assigned....these settings you cannot change...
This linkage you can view in OLMW-----> Account Determination -
> Acc. Determination W/O Wizard -
>Account Grouping....also
Reward if useful
Regards
S.Baskaran
Edited by: baskaran srinivasan on Dec 20, 2007 12:18 PM

Configured Sales Order Items using BAPI_SALESORDER_CREATE

Hello
I am trying to use the BAPI_SALESORDER_CREATEFROMDAT2 to create a Sales Order for a Configured Item .
I get my item on the Sales Order but no Configuration Data behind it .
I am populating the the order_items_in & order_items_inx tables and linking using po_itm_no fields .
I am also populating the order_cfgs_ref , order_cfgs_inst , order_cfgs_value fields with the relevant Characteristics data .
I have looked at the SAP Note 549563 and can see no differences between the info on that and what I am doing .
Does anyone have any advice or experience of doing this ?
Regards
Paul

Hi all,
I managed to create a dummy sales order in SAP R/3 using the DCOM Connector and Borland Delphi 7.0 Professional.
Hoping the below listed example will help, here we go:
    ctrlBAPI: TSAPBAPIControl;
var
order, header, items, partners, ret: Variant;
     try
           order := ctrlBAPI.GetSAPObject('SalesOrder');
           header := ctrlBAPI.DimAs(order, 'CreateFromDat1', 'OrderHeaderIn');
           items := ctrlBAPI.DimAs(order, 'CreateFromDat1', 'OrderItemsIn');
           partners := ctrlBAPI.DimAs(order, 'CreateFromDat1', 'OrderPartners');
           ret := ctrlBAPI.DimAs(order, 'CreateFromDat1', 'Return');
           // The values....
           header.Value('DOC_TYPE') := 'TA';
{ the order type is as you see it when you log in with language 'DE' }
           header.Value('SALES_ORG') := '2000';
           header.Value('DISTR_CHAN') := '10';
           header.Value('DIVISION') := '10';
           header.Value('REQ_DATE_H') := now;
           header.Value('PURCH_NO') := 'Test BAPI Delphi';
           partners.Rows.Add;
           partners.Value(1, 'PARTN_ROLE') := 'AG';
{ The partner function is as you see it when you log in with language 'DE' }
           partners.Value(1, 'PARTN_NUMB') := 'M9531057';
           // Line 1...
           items.Rows.Add;
           items.Value(1, 'MATERIAL') := '000000000000000354';
           items.Value(1, 'REQ_QTY') := '00000003';
           // Line 2
           items.Rows.Add;
           items.Value(2, 'MATERIAL') := '000000000000003595';
           items.Value(2, 'REQ_QTY') := '00000005';
           // Insert this order in R/3...
           order.CreateFromDat1( OrderHeaderIn := header,
                   OrderItemsIn := items,
                   OrderPartners := partners,
                   Return := ret);
           ShowMessage('Return type: ' + ret.Value('TYPE') + #13 + 'Message: ' + ret.Value('MESSAGE'));
        except
                on E:Exception do
                        ShowMessage(E.Message)
        end;
If you need more help, do not hesitate to ask,
Bogdan CIOC

Error in sales order when selecting a warranty item in configurator 'Please enter required information - Service Reference Type Code'

Error in sales order when selecting a warranty item in configurator 'Please enter required information - Service Reference Type Code'
Not able to book the sales order because of this issue

Order Management does not support the inclusion of optional service items in a configured Model BOM (see Support article #1296751.1 for more detail). Allowing for such would therefore require customization.
As you've found, there's no modeling restriction that prevents you from creating a Model BOM that includes optional service items, nor is there any problem with creating a Configurator Model for it. And required service items (such as a warranty item that is a required child of an optional BOM component) do not present a problem; they have nothing to do with Configurator, and would never appear as sub-lines in OM. The problem arises in OM, which requires that any service item be "associated" to the item it's "servicing". OM does not automatically make such an association with service sub-lines, even though it might be argued that an association may be inferred by the BOM structure (i.e., OM does not assume that an optional service sub-line is necessarily associated, from a service standpoint, with its BOM parent). OM customization is therefore required in order to hook any service item up to its corresponding product item. Many customers who configure service along with product have implemented such a customization.
(Another gap in such a solution that may be relevant to you is that for an included optional service item requiring recurring billing, Order Management does not create the requisite Service Contract. Customers have likewise developed customizations to address this, as well.)
As this is not specifically a Configurator matter (you could have created your order without using Configurator at all, and you would have experienced the exact same behavior), please do not take my explanation as being either authoritative or comprehensive (I am a Configurator expert, and only knowledgeable enough about Order Management to be dangerous). It would be advisable for you to seek more detailed information/recommendations from the Order Management forum.
Eogan

How to block a sales order when there is a free good item .

Hello Gurus ,
How to block a sales order when there is a free good item , only the authorised person should have authorisation to release those blocked Sales orders.
Reason - They want to have a track of free goods given to customer & to avoid the misusing things
Looking for your inputs
Thanks in advance
Regards
Venkat

Hi
I think you can try with Status Profile in BS02 define and assign for item category TANN.
In status profile you can block the delivery and also billing unless some changes the object status as released.
Just try and explore
regards
Prashanth

How to place a credit block on a Sales order

Hi All,
I am creating a scenario for testing in which I have to place a credit block on a Sales order. How do I do that. Please help.
Regards,
Shanu

>
Shanu Jain wrote:
> Hi Ravi,
>
> Thank you for the response. If I want to get the error of credit block while creating the Sales order itself (when I am trying to save the Sales order) what settings we need to do besides making the credit limit zero for that customer in FD32?
>
> Regards,
> Shanu.
Hi Shanu,
Just do simple debugging and change the field value , it will automatically solve your purpose , with this there is no need to change the configuration etc.
pls put the break point at ..
1) Goto tcode se38. Here input SAPLVKMP and then press display.
2) here you can see lot of includes , here pls double click on the include LVKMPF0A.
3) Here you will see the code like..
open values > creditlimit
IF SCC_SUM_OPENS GT SAV_KNKK_KLIMK.     :> place the break point here
    PERFORM MESSAGE_EXCEEDED_VALUE USING SCC_FLG_ORDER SCC_SUM_OPENS.
    MOVE CON_RC_NOK TO SCC_RC.
ENDIF.
4) And now do the sales order , the cursor reaches here , then in the debugging mode change the value of SCC_SUM_OPENS to more than SAV_KNKK_KLIMK.
5) And then press f8 , now you will get the desired result , ie your order will have a credit block.
Hope this will help you.
Regards,
Vvieks

How to make a field in sales order a required field

Hi,
How do i make a certain field in sales order a required field. I want to make the assignment field in accounting tab a required field. How do i configure this.
Thank you.
Rachelle

In you know the Transaction and screen Variant Configurations.
Use T-code SHD0
Put your Sales Order t-code There : Va01
Then Select the feilds or tabs whatever you want as mandatory , optional.
Customize as per your requirement and save the variant.
Next GO to the Sales Document types :
There In the Transaction flow you will find at variant feild.
Assign this variant there.
Next when ever you do sales Order for that Document type the feilds will be taken in the fashion of the variant.
regards,
SAP SD

Exclude condition from sales order when minimum vale not reached

Hello,
what would be the best way to exclude/include the freight cost condition from sales order when minimum order value is not reached?
Thanks and best regards
L

Hi,
If you want to be it should be automatically then follow what RAM KI suggested, but without much more work you want do it manually then do as suggested below
Use the field USAGE at header >> under Sales tab
Create table with combination of Sales orgz and usage fileld and generate table
Assign this generated table to access sequence which is used in your frieght condition
Configure two usages as FRIEGHT include and FRIEGHT Exclude
Maintain condition record for the frieght condition with above combination
Now when you create sales order go header level and select usage as you select usage system will pull values from condition record for frieght.
kapil

VERSION FIELD FROM SALES ORDER NOT APPEARING IN COOIS REPORT

DEAR ALL,
I am working on make to order scenario. Version field from sales order not updated when im taking MRP Run for specific Sales order in COOIS Report. But when iam creating production order with T. COde CO08 field getting updated. Its very important to get vrsion field as we have maintain old sales order No. in same. How this problem will get resolved?
Regards
Atul

Atul,
"MRP run" does not normally create production orders, MRP creates Planned orders. Planned orders do not contain Sales order version. I have never used this field before, but I would not be surprised if the behavior you are describing is 'standard'. When you create a production order using CO08, you are creating a 'production order with reference to a Sales order' (which contains Sales Version). When you create a production order using, say, CO40 or CO41, or using a program such as PPBICO40 in Batch, you are creating a 'production order with reference to a Planned order', (which does not contain version).
If it is imperative that you have the Sales Order version number in all production orders, you could see if Planning Strategy 82 (Assemble to order) production orders contain the data you seek. Otherwise, I am afraid you will have to have your ABAPers write some custom code to update this field in the production order.
Another way to get sales order data into the production order, that does NOT require custom code, is by using Item Texts in the Sales order. Any text placed in the Sales Order Item Text Field Production Memo (Text ID 0006) can be configured to be duplicated automatically in the Production order in an MTO environment. Production Memo then displays as another Tab in CO02.
Regards,
DB49

Reason of rejection field in sales order

Hi All,
For a sales order when we create subsequent document i.e delivery...etc the reason for rejection field at item level gets Grayed out and the function module BAPI_SALESORDER_CHANGE is not updating it and returining the message " Field 'ABGRU' cannot be changed, VBAPKOM 000001 ready for input."
Is there any other function module or any other way to update the ABGRU i.e reason for rejection in sales order?
any help will be highly appreciated.:)
regards,
pavan.

Basically BAPI do the direct update to the tables, it will cross check with the configurations settings and not allowing to do the change for the particular field. Try to make it modifiable and run your BAPI it should work.

How to add a field in sales order

Dear All,
First I created a ZTable in which there are 15 fields exist then I append structure in ZVBAP which contain only one field from this ZTable. Now I place this field in the Subscreen 8459 of Sales Order under "Additional Data B" by using access key. Also i have Access to edit the module MV45AFZZ.
Then I wote the code in the
FORM userexit_save_document_prepare.
IF XVBAP-ZZSPENR = ''.
MESSAGE 'SPECIFICATION NO. IS NOT SPECIFIED' TYPE 'E'.
ELSE.
VBAP-ZZSPENR = ZSPEC-ZSPENR.
ENDIF.
ENDFORM.
so that while saving it Checks that field in screen and then if it has value then save it to in the VBAP Table.
I think I have to write the code into the module
FORM userexit_move_field_to_vbap.
VBAP-zzfield = xxxx-zzfield2.
*{   INSERT         ID3K908846                                        1
DATA: zlgort LIKE vbap-lgort.
IF vbap-pstyv EQ 'ZWP'.
    CHECK vbap-lgort IS INITIAL.
    GET PARAMETER ID 'LAG' FIELD zlgort.
    vbap-lgort = zlgort.
ENDIF.
*}   INSERT
WA_XVBAP-ZZSPENR = xvbap-zzspenr. "but this line gives * me error cause I have to move the screen fields into * the VBAP Table. So that after this it checks in internal table XVBAP that the field ZZSPENR has value or not ?
ENDFORM.
But when I checks XVBAP TAble it shows all entries that I fill in Sales Order except ZZSPENR (My Field)
Thanks in advance.
Regards.
Adams.
Helpful answer will be appretiated.

hi Amams
check this link
Adding Fields to Sales order
i think it may give u some idea
Regards,
Naveen

Blocked field in Sales Order when using configurable materials

Similar Messages

Maybe you are looking for