Retail : Mass characteristic value change

Hi,
I manage characteristic values in the material master data (MM41/MM42/MM43) but I did not find a way to change these values in mass (MM46).
Does someone has an idea ?
Best regards,
ML

Hi,
Pls put in MM forums and get the reply immly.
Anil

Similar Messages

Generate change documents for characteristic value changes in material master

Hello,
I am currently using material class (class type: 001) and assign some characteristics to material master. I am going to create a query/custom report to track all changes in the characteristic values in that material master. However, I could not find any change document in CDHDR table.
I have activated "Change Docs" parameter in class type 001 customizing as described in SAP note: 65124 Classification Change Documents as follow:
Is it possible to generate change documents for characteristic values in material master?
Regards,
Julian

Hi Rajen,
Thanks for your reply. It seems that I missed one more step in the customizing. Once the multiple object is activated, I need to activate the change document parameter for each assigned object.
Thread closed.
Regards,
Julian

BI-IP: Change of characteristic value in ABAP EXIT planning function

Hi
I have created a planning function of the type EXIT with reference data without blocks. In method IF_RSPLFA_SRVTYPE_IMP_EXEC_REF~EXECUTE I am going to implement my code.
Now, one of the purposes is to update the VALIDTO of an existing record. Is it possible to modify the characteristic values directly in C_TH_DATA (thus allowing me to just update the date directly on the record) or can I only append records?
Cheers!
/Karsten

Hi Larse,
Yes you can change directly your value in a record withou appending a new one,but still it will create 2 records in the delta buffer ready to be save to the cube.
Reagrds,
Eitan.

BI-IP change characteristic value in FOX

Hello Guys,
i want to change the characteristic value in FOX.
Therefore the FOX runs through all char combinations to identify the highest
number for the char test.
This step works fine, but i cant write the value for maxloop in the cube.
If i try, only the old row is deleted, but i dont get a new row with the calculated value for maxloop.
the code looks like this:
DATA LOOP TYPE test.
DATA MINLOOP TYPE test.
DATA MAXLOOP TYPE test.
MINLOOP = 00000.
MAXLOOP = 00000.
FOREACH LOOP.
MINLOOP = LOOP.
IF MINLOOP > MAXLOOP.
MAXLOOP = MINLOOP.
ENDIF.
ENDFOR.
MAXLOOP = MAXLOOP + 00001.
{Amount, EUR, #, #, 00200, 00000000, #, 2007, #, #, #, #, #, #, #} =
{Amount, EUR, #, #, maxloop, 00000000, #, 2007, #, #, #, #, #, #, #}.
Any suggestions what is wrong here?
Regards
T. Mekler

Hi,
You have written
{Amount, EUR, #, #, 00200, 00000000, #, 2007, #, #, #, #, #, #, #} =
{Amount, EUR, #, #, maxloop, 00000000, #, 2007, #, #, #, #, #, #, #}.
But as per the statement MAXLOOP = MAXLOOP + 00001 the MAXLOOP conatins a new figure. Obviously there will not be any record in the cube for this value of MAXLOOP.
You are assigning this to the record with MAXLOOP = 00200, so system is assigning zero to 0AMOUNT for the record that is having MAXLOOP=00200 value.
Make the below corrections and test again:
DATA NEWLOOP type test.
NEWLOOP = MAXLOOP + 00001.
{Amount, EUR, #, #, NEWLOOP, 00000000, #, 2007, #, #, #, #, #, #, #} =
{Amount, EUR, #, #, MAXLOOP, 00000000, #, 2007, #, #, #, #, #, #, #}.
Regards,
Deepti

Hi. i used Function module to change Characteristic values of a sales order

hi. i used Function module to change Characteristic values of a sales order..
but sales order's Characteristic values didn't change.
And the Function module doesn't occur any log message.
please tell me wrong code, and how to solve this problem.
if i have wrong method, what data can i pass to change the characteristic values
DATA: LT_E1CUVAL TYPE TABLE OF E1CUVAL.
DATA: WA_E1CUVAL TYPE E1CUVAL.
DATA: LS_CFG_HEAD LIKE CUXT_CUCFG_S,
 LS_INSTANCES LIKE CUXT_CUINS_S,
 LS_VALUES LIKE CUXT_CUVAL_S,
 LS_E1CUCFG LIKE E1CUCFG,
 LS_E1CUINS LIKE E1CUINS,
 LS_E1CUVAL LIKE E1CUVAL,
 LS_PROFILE LIKE E1CUCOM,
 LS_VBAP LIKE VBAP,
 L_CUOBJ LIKE INOB-CUOBJ,
 L_ATINN LIKE CABN-ATINN.
DATA: LT_INSTANCES LIKE CUXT_CUINS_S OCCURS 0,
 LT_PART_OF LIKE CUXT_CUPRT_S OCCURS 0,
 LT_VALUES LIKE CUXT_CUVAL_S OCCURS 0,
 LT_VAR_KEYS LIKE CUXT_CUVK_S OCCURS 0,
 LT_KSML LIKE KSML OCCURS 0 WITH HEADER LINE,
 BEGIN OF LT_CLINT OCCURS 0,
 CLINT LIKE KSSK-CLINT,
 END OF LT_CLINT.
DATA: LT_CUIB LIKE CUIB_CUOBJ_S OCCURS 0 WITH HEADER LINE.
DATA: E_ROOT_INSTANCE TYPE CUXT_INSTANCE_NO.
DATA: EV_ROOT_PERSIST_ID TYPE IBEXTINST_DATA-EXT_INST_ID.
DATA: EV_CFG_HAS_CHANGED TYPE XFELD.
DATA: EV_HANDLE_APPL_LOG TYPE BALLOGHNDL.
DATA: L_CUOBJ_NEW TYPE CUOBJ.
DATA: L_OWNER TYPE IBXX_BUSINESS_OBJECT.
REFRESH LT_E1CUVAL.
CLEAR LS_VBAP.
SELECT SINGLE CUOBJ INTO CORRESPONDING FIELDS OF LS_VBAP
 FROM VBAP WHERE VBELN = I_VBELN
 AND POSNR = I_POSNR.
IF SY-SUBRC <> 0.
 RAISE INSTANCE_NOT_FOUND.
ENDIF.
REFRESH LT_CUIB. CLEAR LT_CUIB.
LT_CUIB-INSTANCE = LS_VBAP-CUOBJ.
APPEND LT_CUIB.
CALL FUNCTION 'CUCB_INITIALIZER'
 EXPORTING
 IT_INSTANCES = LT_CUIB[].
CALL FUNCTION 'CUXI_GET_SINGLE_CONFIGURATION'
 EXPORTING
 I_ROOT_INSTANCE = LS_VBAP-CUOBJ
 IMPORTING
 E_CFG_HEAD = LS_CFG_HEAD
 ES_PROFILE = LS_PROFILE
 ET_RETURN = ET_RETURN
 TABLES
 E_TAB_INSTANCES = LT_INSTANCES
 E_TAB_PART_OF = LT_PART_OF
 E_TAB_VALUES = LT_VALUES
 E_TAB_VAR_KEYS = LT_VAR_KEYS
 EXCEPTIONS
 INVALID_INSTANCE = 1
 NO_ROOT_INSTANCE = 2
 INSTANCE_IS_A_CLASSIFICATION = 3
 INTERNAL_ERROR = 4
 NO_PROFILE_FOUND = 5
 INVALID_DATA = 6
 OTHERS = 7.
IF SY-SUBRC <> 0.
 CASE SY-SUBRC.
 WHEN 1.
 RAISE INSTANCE_NOT_FOUND.
 WHEN 3.
 RAISE INSTANCE_IS_A_CLASSIFICATION.
 WHEN OTHERS.
 RAISE INVALID_DATA.
 ENDCASE.
ELSE.
 LOOP AT LT_VALUES INTO LS_VALUES.
 IF LS_VALUES-CHARC = 'SAP_MILLCA_PACKAGING'
 OR LS_VALUES-CHARC = 'PD_CA_PACKING_DM'.
 LS_VALUES-VALUE = '7100010'. "This is test data
 MODIFY LT_VALUES FROM LS_VALUES.
 ELSE.
 DELETE LT_VALUES WHERE CHARC = LS_VALUES-CHARC.
 ENDIF.
 CLEAR LS_VALUES.
 ENDLOOP.
ENDIF.
영업정보 특성 변경
CALL FUNCTION 'CUXI_SET_SINGLE_CONFIGURATION'
 EXPORTING
 I_CFG_HEADER = LS_CFG_HEAD
 I_ROOT_INSTANCE = LS_VBAP-CUOBJ
 I_PLANT =
 I_STRUCTURE_EXPLOSION_DATE =
 I_STRUCTURE_EXPLOSION_APPL_ID =
 I_LOGSYS =
 IS_PROFILE = LS_PROFILE
 IV_ONLY_SINGLE_LEVEL =
 IV_HANDLE_APPL_LOG =
 IV_OBJECT_APPL_LOG = 'CIF'
 IV_SUBOBJECT_APPL_LOG = 'T_CNFG'
 IMPORTING
 E_ROOT_INSTANCE = E_ROOT_INSTANCE
 EV_ROOT_PERSIST_ID = EV_ROOT_PERSIST_ID
 EV_CFG_HAS_CHANGED = EV_CFG_HAS_CHANGED
 EV_HANDLE_APPL_LOG = EV_HANDLE_APPL_LOG
 ET_RETURN = ET_RETURN
 TABLES
 I_TAB_INSTANCES = LT_INSTANCES
 I_TAB_PART_OF = LT_PART_OF
 I_TAB_VALUES = LT_VALUES
 I_TAB_VAR_KEYS = LT_VAR_KEYS
 I_TAB_BLOB =
 EXCEPTIONS
 NO_CONFIGURATION_DATA = 1
 NO_ROOT_INSTANCE = 2
 INVALID_INSTANCE = 3
 INSTANCE_IS_A_CLASSIFICATION = 4
 INTERNAL_ERROR = 5
 NO_PROFILE_FOUND = 6
 INVALID_DATA = 7
 OTHERS = 8
IF SY-SUBRC <> 0.
 CASE SY-SUBRC.
 WHEN 1.
 RAISE NO_CONFIGURATION_DATA.
 WHEN 3.
 RAISE NO_ROOT_INSTANCE.
 WHEN 3.
 RAISE INVALID_INSTANCE .
 WHEN 3.
 RAISE INSTANCE_IS_A_CLASSIFICATION.
 WHEN 3.
 RAISE INTERNAL_ERROR.
 WHEN OTHERS.
 RAISE INVALID_DATA.
 ENDCASE.
ENDIF.
COMMIT WORK.
save configuration with next commit
CLEAR: LS_INSTANCES.
READ TABLE LT_INSTANCES INTO LS_INSTANCES INDEX 1.
L_OWNER-OBJECT_TYPE = LS_INSTANCES-OBJ_TYPE.
L_OWNER-OBJECT_TYPE = 'PVS_POSVAR'.
L_OWNER-OBJECT_KEY = LS_INSTANCES-OBJ_KEY.
CALL FUNCTION 'CUCB_CONFIGURATION_TO_DB'
 EXPORTING
 ROOT_INSTANCE = LS_VBAP-CUOBJ
 ROOT_OBJECT = L_OWNER
 IMPORTING
 NEW_INSTANCE = L_CUOBJ_NEW
 EXCEPTIONS
 INVALID_INSTANCE = 1
 INVALID_ROOT_INSTANCE = 2
 NO_CHANGES = 3
 OTHERS = 4.
IF SY-SUBRC > 1 AND SY-SUBRC <> 3.
 CLEAR LS_VBAP-CUOBJ.
 RAISE INTERNAL_ERROR.
ELSEIF SY-SUBRC = 1.
 LS_VBAP-CUOBJ = L_CUOBJ_NEW.
ENDIF.
What's wrong?
help me to solve this problem.
Thanks a lot.

SD_SALES_DOCUMENT_READ Reads sales document header and business data: tables VBAK, VBKD and VBPA (Sold-to (AG), Payer (RG) and Ship-to (WE) parties)
SD_SALES_DOCUMENT_READ_POS Reads sales document header and item material: tables VBAK, VBAP-MATNR
SD_DOCUMENT_PARTNER_READ partner information including address. Calls SD_PARTNER_READ
SD_PARTNER_READ all the partners information and addresses
SD_DETERMINE_CONTRACT_TYPE
In: at least VBAK-VBELN
Exceptions: NO CONTRACT | SERVICE_CONTRACT | QUANTITY_CONTRACT
SD_SALES_DOCUMENT_COPY
RV_ORDER_FLOW_INFORMATION Reads sales document flow of sales document after delivery and billing
SD_SALES_DOCUMENT_SAVE create Sales Doc from the copied document
SD_SALES_DOCUMENT_ENQUEUE to dequeue use DEQUEUE_EVVBAKE
RV_DELIVERY_PRINT_VIEW Data provision for delivery note printing
SD_PACKING_PRINT_VIEW
SD_DELIVERY_VIEW Data collection for printing
called from RV_DELIVERY_PRINT_VIEW, SD_PACKING_PRINT_VIEW
RV_BILLING_PRINT_VIEW Data Provision for Billing Document Print
regards
vinod

How to change the characteristic value in a item of sales order by FM?

Hi experts,
I guess the FM BAPI_SALESORDER_CHANGE can implement my requirement. But I have made many testing program, that's all failed. I don't know which part is not correct. So could you give a very simple sample to me? Just change the characteristic value in a item of sales order, not do any change for other parts. Thanks in advanced.
Regrads

Hi Birendra,
Thanks for you explain. I follow your guide to wirte abap program. But related characteristic value still not changed in SO main screen. could you give me some suggestion? Thanks a lot!
type-pools: IBCO2,
 IBXX.
data: l_CUOBJ type CUOBJ_VA,
 l_ibase type IBCO2_IBASE_REC,
 l_CONFIGURATION type IBCO2_INSTANCE_TAB2,
 w_CONFIGURATION type IBCO2_INSTANCE_REC2,
 l_ROOT_OBJECT type IBXX_BUSINESS_OBJECT.
data: t_IBCO2_VALUE_TAB type IBCO2_VALUE_TAB,
 w_IBCO2_VALUE_REC type IBCO2_VALUE_REC.
select single CUOBJ
into l_CUOBJ
from VBAP
where VBELN = '0020030609'
 and POSNR = '000020'.
CALL FUNCTION 'CUCB_GET_CONFIGURATION'
 EXPORTING
 INSTANCE = l_CUOBJ
 IS_BUSINESS_OBJECT =
 IV_MOMENT =
 IV_WITH_DB_INSTANCE =
 IMPORTING
 IBASE = l_ibase
 CONFIGURATION = l_CONFIGURATION
 EO_CBASE_REF =
EXCEPTIONS
 INVALID_INPUT = 1
 INVALID_INSTANCE = 2
 INSTANCE_IS_A_CLASSIFICATION = 3
 OTHERS = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
loop at l_CONFIGURATION into w_CONFIGURATION.
l_ROOT_OBJECT = w_CONFIGURATION-OWNER.
t_IBCO2_VALUE_TAB[] = w_CONFIGURATION-values[].
read table w_CONFIGURATION-values into w_IBCO2_VALUE_REC with key ATINN = '0000000222'.
w_IBCO2_VALUE_REC-ATWRT = 'TMP'.
modify w_CONFIGURATION-values from w_IBCO2_VALUE_REC index sy-tabix.
modify l_CONFIGURATION from w_CONFIGURATION index 1.
clear: w_CONFIGURATION.
endloop.
CALL FUNCTION 'CUCB_SET_CONFIGURATION'
EXPORTING
 ROOT_INSTANCE = l_CUOBJ
IS_CBASE_HEADER =
CHANGING
 CONFIGURATION = l_CONFIGURATION
EXCEPTIONS
INVALID_INPUT = 1
INVALID_INSTANCE = 2
INSTANCE_IS_A_CLASSIFICATION = 3
OTHERS = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'CUCB_CONFIGURATION_TO_DB'
EXPORTING
 ROOT_INSTANCE = l_CUOBJ
 ROOT_OBJECT = l_ROOT_OBJECT
FORCE_NEW_INSTANCE =
IV_WITHOUT_COMMIT_UPDATE = ' '
IV_MATERIAL =
IV_LOCATION =
IV_TECHS =
IMPORTING
NEW_INSTANCE =
TABLES
EXP_NEW_NESTED_CUOBJS =
EXCEPTIONS
INVALID_INSTANCE = 1
INVALID_ROOT_INSTANCE = 2
NO_CHANGES = 3
ALREADY_REGISTERED_FOR_UPDATE = 4
INSTANCE_IS_A_CLASSIFICATION = 5
OTHERS = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Change characteristic values in SO via BAPI_SALESORDER_CHANGEBOS

Hi Experts,
Now, I would like to update the characteristic values of configuration in sales order via BAPI : BAPI_SALESORDER_CHANGEBOS. But, I can't find right way to execute this BAPI. I tried so many times and no data changed. I wonder that i didn't specify the correct import parameters.
Is anyone can help me? Thanks for your kindly support in advance.
Best Regards,
Ryan

Hi Ryan,
I had a similar kind of requirment, to change the characteristic values in a sales contract, where I used, BAPISDORDER_GETDETAILEDLIST to get the details of the agreement line iteam and after sorting the necessary vales then used BAPI: BAPI_CUSTOMERCONTRACT_CHANGE to change the customer agreement line item.
In your case as well you can use the BAPISDORDER_GETDETAILEDLIST to get the details, based on this you write logic to hold the necessary change value and finally, use BAPI: BAPI_SALESORDER_CHANGE to updated the changes in the sales order.
Hope this helps.
Regards
Raj

Changing DATE as a Characteristic value of batch with BAPI_OBJCL_CHANGE

Hello,
Could you give advice for using BAPI_OBJCL_CHANGE?
I decided to use BAPI_OBJCL_CHANGE to update Batch characteristic value.
I could update CHAR field but could not DATE.
I set like below :
- Characteristic name (e.g. Z10001) to CHARACT of ALLOCVALUESNUMNEW(Tables)
- DATE(e.g. 20081211) to VALUE_FROM of ALLOCVALUESNUMNEW(Tables).
But it does not work.
Of course, I executed BAPI_TRANSACTION_COMMIT after the FM done.
I found the value of VALUE_FROM is missing when debugging.
Thanks in advance.
Takeru Miyagawa

Hello,
you said :
- DATE(e.g. 20081211) to VALUE_FROM of ALLOCVALUESNUMNEW(Tables).
Data type of field VALUE_FROM is FLTP. How do you fill this field ? by MOVE ?
You should not use MOVE, you should use :
DATA:
wlv_date              TYPE d,
wls_ALLOCVALUESNUMNEW TYPE BAPI1003_ALLOC_VALUES_NUM.
           CALL FUNCTION 'CTCV_CONVERT_DATE_TO_FLOAT'
                         EXPORTING date          = wlv_date
                         IMPORTING   float       = wls_ALLOCVALUESNUMNEW-VALUE_FROM.
- I found the value of VALUE_FROM is missing when debugging.
Can you show us your code ?
Cordialement,
Chaouki.

Slow dataload into Infocube- Conversion of Characteristic values to SIDs

Hi All,
we are facing a slow delta load issue when loading from a DSO into an InfoCube ( approx 150,000 recs).
After checking the monitor found that
- The Conversion of Characteristic values to SIDs is taking time
- The Start Routine time is real quick ( in secs)
The underlying DSO is hugh and there is no SIDs Generation upon Activation flag set for it
Master data is loaded first and than we are loading the transaction data.
i've tried refreshing the stats of the Cube, Reduce the size of the data package,
Deletion of Indexes than Loading and recreation of Indexes, no joy at all.
Any comments and recommendations are much appreciated.
Thanks,
Natalie

Hi Natalie,
The problem for your slow delta load from DSO to cube is because the SIDs Generation upon Activation flag is unchecked at DSO level .
Becasue of which your activation is faster but your loading from DSO to cube will be slower as you only mentioned that SIDs are being generated .
One recommendation will be to switch on the property of the DSO SIDs Generation upon Activation flag .
Are there any secondary indexes also in DSO ?
You can try deleting them also during loading the data from DSO to cube .
I guess your change log table is also huge in this case . If possible we can think of deleting the log table also . Then for the new records let it get filled .
Hope the above reply was helpful.
Regards,
Ashutosh Singh .
Edited by: DEADLOCKS on Apr 21, 2011 5:08 PM

Characteristic value '5000000000 ' of characteristic 0MATERIAL is not MATN1

Dear Experts,
I am getting one error message while extraction,when executing the DTP .the messge is :
"Characteristic value '5000000000 ' of characteristic 0MATERIAL is not MATN1 -converted" BRAIN 68 @3R@
what is the meaning of this messege ,Request you to plese suggest me reagarding the same .thanks in advance .

Hi Bhullar,
Have you maintained material length as 18 at ECC and BW sides.
at bw side info object 0material conversion routine as MATN1. seems like you may be maintained as ALPHA. if your using as ALPHA conversion routine then at transfer rules for MATERIAL you can pass output data by suing FM - CONVERSION_EXIT_ALPHA_INPUT.
or if possible then change conversion routine to MATN1 for material(info obj) at data source level or info object maintenance(RSD1) level.
Thanks

Copy BOM Component Characteristic value in material PR created by MRP Run

Dear Gurus,
My requirement is I have materials like thread to maintain color characteristic i have create class - color- class type is 023 , now i want user should able to maintain characteristic value in BOM component (thread) of semifinish material. FG , SFG are not having any characteristic.
Now in PR and PO we can maintain characteristic value in Material Data --->Configuration tab , Configuration tab will come only when there is tick in material is configurable at material basic data 2 view of thread and in CU41 I have to maintain material for class type 300 - Variant , then in class assignment i have select class type 300 and 023 both and maintain class , both are having same characteristic please make me correct if i am doing wrong process, if i am not maintaining class assignment 300 in CU41, in manual PO system not allowing to enter characteristic value in configuration tab . so i maintain both class assignment 300 and 023.
Now for manual PR and PO system showing configuration tab and from PO configuration tab characteristic value is coming in MIGO automatically but when i am running MRP for finish material the auto PR generated by system for material thread is not showing configuration tab in Material Data of PR. I have maintain characteristic value in BOM --->Extra--->Batch Classification. Please guide me how to archive this.
Thanks & Regards
Akshay.

Akshay kukde,
Still i am unable to understand the reason for maintaining a characterstic value for a batch through BOM, I hope you are not changing BOM for every purchase order ?
can you explain what you expect by maintaing this one value for batch characterstic?
you can have many other simple option like
1) Create a material with colour included in it ex, Thread_red, Thread _green etc and use them in BOM
2) Use text in BOM to hold this discription for colour
3) Use batch management, class 023 in material master classification , defalut value for colour, purchase order will be created and while doing GR you can change in colur if its different then default you set earlier.
Akshay kukde wrote:
if i am creating PR Manually -ME51N , system showing configuration tab , where i can maintain characteristic value , which then reflecting in PO and from PO to MIGO
The above scenario I have tried by maintaining class type 023 and same characteristic in material Master. but result is same for auto generate PR by MRP- configuration tab is missing.
My requirement in this case is characteristic value should flow from BOM to PR generated by MRP.
when you manualy create PR you Thread material is consider to be a configurable material and thats why you are able to input configuration value, otherwise as soon as you put this configurable material inside a BOM of normal materila it loost its configuration feature, if you want you can create your parent material also as configurable material, assign same class to it and create configuration profile and take MRP run this time you will get PR with configuration tab as your thread get configuration derived from parent.
Hope above details may help you.
Check and reply, also mark replies helpful if it helps you.
Thanks
Ritesh

Characteristic values in BAPI_SALESORDER_CHANGE

Hi,
I want to add new configurable item in existing sales order with charactersitic values.
Iam using bapi BAPI_SALESORDER_CHANGE.
Iam now able to insert configurable item in existing sales order.
But the characteristic values are not getting stored.
Latest code is attached. What else is missing for storing characteristic values ?
select maximum item number in sales order
SELECT MAX( POSNR ) FROM VBAP CLIENT SPECIFIED
INTO MAX_POSNR
WHERE MANDT = SY-MANDT AND
VBELN = I_SORDER.
TMP_POSNR = MAX_POSNR + 10.
WA_HDRX-UPDATEFLAG = 'U'.      "update
SALES_DOC = I_SORDER.
item data
WA_ITEM-ITM_NUMBER = TMP_POSNR.
WA_ITEM-MATERIAL   = 'LEFTEYE'.
WA_ITEM-PLANT      = I_STORE.
WA_ITEM-SHIP_POINT = I_STORE.
APPEND WA_ITEM TO IT_ITEM.
WA_ITEMX-ITM_NUMBER = TMP_POSNR.
WA_ITEMX-UPDATEFLAG = 'I'.      "add
WA_ITEMX-MATERIAL   = 'X'.
WA_ITEMX-PLANT      = 'X'.
WA_ITEMX-SHIP_POINT = 'X'.
APPEND WA_ITEMX TO IT_ITEMX.
Schedule lines
WA_SCHD-ITM_NUMBER = TMP_POSNR.
WA_SCHD-SCHED_LINE = TMP_POSNR.
WA_SCHD-REQ_DATE   = SY-DATUM.
WA_SCHD-REQ_QTY    = 1.
WA_SCHD-SCHED_TYPE = 'CN'.
APPEND WA_SCHD TO IT_SCHD.
WA_SCHDX-ITM_NUMBER = TMP_POSNR.
WA_SCHDX-SCHED_LINE = TMP_POSNR.
WA_SCHDX-REQ_DATE   = 'X'.
WA_SCHDX-REQ_QTY    = 'X'.
WA_SCHDX-SCHED_TYPE = 'X'.
APPEND WA_SCHDX TO IT_SCHDX.
config & characteristic values
WA_VALUE-CONFIG_ID = '000001'.
WA_VALUE-INST_ID   = '00000001'.
WA_VALUE-CHARC     = 'PRES_DIST_SPH'.
WA_VALUE-VALUE     = '3.2'.
APPEND WA_VALUE TO IT_VALUE.
WA_INST-CONFIG_ID = '000001'.
WA_INST-INST_ID    = '00000001'.
WA_INST-OBJ_TYPE   = 'MARA'.
WA_INST-CLASS_TYPE = '300'.
WA_INST-OBJ_KEY    = 'LEFTEYE'.
WA_INST-QUANTITY   = 1.
WA_INST-QUANTITY_UNIT = 'NO'.
APPEND WA_INST TO IT_INST.
WA_REF-POSEX     = TMP_POSNR.
WA_REF-CONFIG_ID = '000001'.
WA_REF-ROOT_ID   = '00000001'.
APPEND WA_REF TO IT_REF.
WA_PART-CONFIG_ID = '000001'.
WA_PART-PARENT_ID = '00000001'.
WA_PART-INST_ID    = '00000001'.
WA_PART-OBJ_TYPE   = 'MARA'.
WA_PART-CLASS_TYPE = '300'.
WA_PART-OBJ_KEY    = 'LEFTEYE'.
APPEND WA_PART TO IT_PART.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT      = SALES_DOC
ORDER_HEADER_INX   = WA_HDRX
TABLES
RETURN                         = IT_RET
ORDER_ITEM_IN             = IT_ITEM
ORDER_ITEM_INX            = IT_ITEMX
ORDER_CFGS_REF         = IT_REF
ORDER_CFGS_PART_OF = IT_PART
ORDER_CFGS_INST        = IT_INST
ORDER_CFGS_VALUE    = IT_VALUE
SCHEDULE_LINES          = IT_SCHD
SCHEDULE_LINESX        = IT_SCHDX.
READ TABLE IT_RET INTO WA_RET WITH KEY TYPE = 'E'.
IF SY-SUBRC = 0.
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ENDIF.
I get the following messages from BAPI :
ORDER_HEADER_IN has been processed successfully.
ITEM_IN has been processed successfully
The sales document is not yet complete: Edit data
TIL-Direct Sales TINDC01372 has been saved
What else is missing ? Any help is appreciated.
thanks,
Nagarajan.J

Hello Nagarajan,
I have used this BAPI in my last task. You are passing the values correctly. I will tell you why it is giving like that message.
Whenever we will create a sales order in VA01 transaction, you will get a message like "The sales order is not complete, would you like to EDIT" while saving the sales order.... This is because of not providing complete data required for careation of sales order.
Try to implement the changes manually in VA02, if you get same errors, then you can find your code is correct.
Even I got same type of messages when changing a sales order to change the Rejection Reason for the items.
Best Regards,
Sasidhar Reddy Matli.
Edited by: Sasidhar Reddy Matli on Jul 31, 2008 2:20 PM

Best practice for updating ATWRT (Characteristic Value) in AUSP

I've notice that when we change the Characteristic Value of a Classification, that it does not update in the MM record. We have to go into MM02 for each material number that references Char Value and manually change it for row in AUSP to get updated.
Should i just create a report to Loop through and update table AUSP directly? Or is there a better way to do this via a function or BAPI etc? Wanting to know what best practice is recommended.

Hi Scott
You can use a BAPI to do that.
Check the following thread:
BAPI to update characteristics in Material master?
BR
Caetano

All Dates displayed for "Characteristic Values" in Query Designer

Hello Experts,
We are on BI 7.0, level 13. I am having an issue within the Query Designer with regards to dates. I have a write-optimized DSO that contains 3 date fields (for example, ZDATE1, ZDATE2, and ZDATE3). Each date InfoObject is of type DATS so the system automatically creates it with reference to 0DATE.
When I create a query in the Query Designer, on the left hand side, I expand the "Characteristic Values" node under each date field. The Query Designer shows the same list of values for each of the 3 dates even though they are not valid values posted in the DSO for those fields.
For example, ZDATE1 only has 1 value posted in the DSO (01/01/2005).
ZDATE2 only has 1 value posted in the DSO (01/01/2006).
ZDATE3 only has 1 value posted in the DSO (01/01/2007).
Bute when I expand the "Characteristic Values" node in the Query Designer, I see ALL THREE values under each date field. I would expect to only see the 1 value posted for the InfoObject in the DSO. Also note that each InfoObject is defined to show "Only posted values in InfoProvider".
It appears that Query Designer will show all values for the reference InfoObject 0DATE instead of the ones posted to the actual InfoObject in the DSO. If I delete the data in the DSO, the Characteristic Values list still remains because they exist in 0DATE. Anyone encounter this before? How can I get the Characteristic Values list to only show posted values for that InfObject?
Thanks for your help!
J

Thanks for the response. I went into the DSO and right clicked on each of the Date fields. I looked at the Provider-specific properties and there is the option for "Query Exec.FilterVal" which only restricts what values appear when restricting during execution, not during query creation.
Is there someplace else I should look or someplace else I can make change to only display posted dates when creating a query? Thanks!

Hide a row or column for characteristic value # in Query Designer

Hi gurus,
I would if we could hide a result row / column if one of the characteristic value is #. The requirement is actually to remove the meaningless row / column from the whole result set. For example, I have a char Material Group in the column. Since not every Material is assigned to a Material Group, I will get the following layout:
Material_Group A
Material_Group B
Material_Group C
Is it possible to define in query designer so that the column with # will automatically not be displayed?
Thanks,
Meng

Hi Meng,
I guess we have the same users..
But there is one thing that is going to make a non sense on the report: if you do not display the "#" for material group, then the total of your query by material group will not be the summation of what is displayed on the screen...and if the user explort the information in Excel (pretty sure they will do so), you will have some calls that your query does not balance....
Based on that assumption, tell the users to assign a material group to the materials, so that this unassigned column disappears. You could even give them a control report listing all the parts that do not have a material group
If this is a standard business rule not to have a material group for all parts, then, what you could do is to change the text for empty rows for Material group, then the "#" will disappear and wil be under the text description you defined.
But keep in mind that your data is made of materials which do not have a material group in their definition, noraml or not ?
PY

Retail : Mass characteristic value change

Similar Messages

Maybe you are looking for