PO to SO IDoc change (ORDCHG) - Extra condition pricing line generated. Why?

Hi guys,
My ECC6 system currently has an IDoc automation setup where creation/change of Purch Order will also trigger creation/change of Sales Order.
By default, condition pricing type will be PB00 or PBXX. I have implemented some code in EXIT_SAPLVEDB_001 to modify PBXX to ZP10.
This is done by modifying KSCHL in condition table DXKOMV in idoc segment E1EDP05.
What i want to achieve is when any current value is changed in the PO for PBXX, this new value should also reflect in ZP10 in the corresponding SO.
This is the problem i am currently facing:
1. First time change PBXX value in PO, ZP10 value in SO is changed correctly.
2. Second time changing the same PBXX line item value in the same PO, a brand new ZP10 line is generated in SO with the new value. The existing ZP10 line remains with old value and becomes inactive.
Is this normal behaviour? How do i ensure that a new ZP10 line does not get generated in the SO but is only being updated when there is an update in the PO?
Please help. Any input would be greatly appreciated.
Thanks in advance!

Hi Vioth,
Did you got solution for thsi i am also facing the same problem.If you konw the solution kindly suggest the solution for this
Thanks in Adavce,
Regards...............Kishore

Similar Messages

How to change the merge condition in OWB generated code

Hi,
This is regarding the OWB generated code for cubes. We required to change the ON condition of MERGE statement. OWB merge the records on the basis of dimension keys only. Is there any ways to provide the customised merge condition or is it possible to add a measure of the cube to be used in ON condition of the merge?

Hi,
cant´t you customize the generated Code in the Database?
I know that owb has the trait to do the following:
If you create a Mapping, etc. the generated Code will be deployed as PL/SQL Package in the Database Schema.
Now you can edit the Code as Schema User right in the Database.
Don´t edit it in the Metadata, only in the Databse.
If you run now any Process in OWB, he´ll execute your edited Code,
´cause he just takes whats still there. :-)
It´s not realy clean, but in most Times that works.
LoneWolf

Change info record condition pricing unit.

i would like to change pricing unit via me12, but the pricing unit can't be modified. how can i achive this. (ps: i change the info record via lsmw.)

are you manage to change the info record price unit using ME12?, i dont think that the price unit can be change after you enter and save it, you need to mark delete the condition line first, then create a new condition line record for that validity period.

Creation of change pointer for condition split

Hi,
We have SAP system which is integrated with PMM(mainly used for pricing).
Scenario is as explained below.
There is one condition record whose validity is from 25/12/2011 to End of TIme (EOT) for one price record.
Assume today (08/02/2012) business created new condition whose validity is 08/02/2012 to EOT for another price.
Now what happened is in condition table split happened one from 25/12/2011 to 07/02/2012 and one more from 08/02/2012 to EOT.
But we observed that while sending the information to PMM system through idoc system is not sending the condiion record 25/12/2011 to 07/02/2012.
*Now question is whether this is SAP standard functionality (not to send Past validity records) or it is custom change specific to company
.*Assume user creates conditon record whose validity is from tomorrow (09/02/2012) to EOT then split happens like 25/12/2011 to 08/02/2012 (which is today) and 09/02/2012 to EOT.
In this case idoc sends both the condition record as 08/02/2012 is today and not in the past.
Thanks and Regards
Raghavendra Pai

FYI... While pricing condition determination in sales order will refer the pricing value from condition record (with proper validity) based on pricing date.
Say, you condition record for base price as PR00.
Rate
UoM
Valid from
Valid to
100
per EA
01.01.2011
31.01.2011
120
per EA
01.01.2012
31.01.2012
Now you are creating a sales order on 09 Feb 2012. But the pricing date is 21.12.2011.
Then system will copy pricing as 100 instead of 120.
This example practical happens when you create sales order with reference to contract or quotation.
Now, in SAP PMM, I hope you are maintaining condition records through Idoc or may be real sync, then you should have provision for accommodate, these change in pricing and validity.
Now question is whether this is SAP standard functionality (not to send Past validity records) or it is custom change specific to company
Now it totally depends on your/client organization/business process requirement.
I hope this can assist you in understanding. If you have any further concern or doubt, do revert back
Regards
JP

Addition Item getting added while posting Sales Order Changes - ORDCHG

Hello,
I have a requirement to post sales order changes - ORDCHG. Now, when I am adding the qualifier 002 at the item segment E1EDP01 with the existing Item number, it is creating another Item in the sales order rather than changing the existing one. What could be the reason? I am passing the below values in to the respective segments.
E1EDK01-ACTION = '003' - Changes in one or more items
E1EDP01-ACTION = '002' Item Changed.
Please advise.
Regards,
Venkata Phani Prasad K

I encountered the same problem. As Vinit pointed out, it looks up the line item using field POSEX on VBAP instead of POSNR. If you want to look up POSNR, you can implement either user-exit ZXVDBU07 or ZXVDBU09 in IDOC_INPUT_ORDCHG and do the following.
Loop through YVBAP and modify the internal table to set POSEX to be equal to POSNR.
This will cause the IDOC to select the correct line item based on POSNR. The only side-effect is that when the order is updated, it will also update field POSEX on table VBAP.

How to change the manual condition type value in change sales order BAPI

Hi All,
My scenario here is, i want to either add/change the manual condition type value during change of SO.
When i'm trying to pass the order_conditions_in and order_conditions_inx tables in 'BAPI_SALESORDER_CHANGE'.
Condition type is coming at item level but the value is setting to zero. Pls. help if anyone has any idea how to handle this.

Siva,
I guess you posted in Wrong Thread. You need to post in WAS section.
check for any BAPI's available in CRM.
Nagesh Ganisetti.

Change Logs for condition record

Hi Experts,
Is it possible to see the Change logs of condition records ?
Regards,
Venkata Prasanna.R

Condition tables do not have change logs.
But you can define that a table log is written.
You do that in SE11
Enter your conditon table, click change, then click the technical settings button and set the indicator to log data changes

Shipment cost - Change definition of condition types

Change definition of condition types in work pricing procedure
hey all ,
we implemented the shipment cost module and now we have to make some changes
in working condition types because the requirements of the customer changed .
is it recomended and what are the effects of changing the definition of condition types
and by that changing working pricing procedures .
for example if i change condition type from D - wight, V - Volume F - Formula to T scale
( and makeing the properchanges in the scale ) or add some more condition the existing pricing
procedures ?
BR
ASA
Edited by: ASA MOKED on May 22, 2009 3:33 PM

hey and thanks for the reply ,
did you make changes in the definition of existing condition types ?
for example change condition calc.type from d-weight to t-scale ?
BR
ASA .

In ALE/IDOC Change Pointer using Maintenance order for message Type

Hi All Expert,
I am using Maintenace order to send via ALE/IDOC(Change ponters), i need standard message Name for Maintenance Order,

Hello,
I'm not sure you're taking the best approch.
Usually when you need to migrate ISU contracts into an ISU-CRM integrated system, you first migrate everything you need in ISU through the VERY powerful migration workbench available (transaction code EMIGALL), and then you replicate your data to CRM via INITIAL download.
That's definitely the strategy that will give you the best performance, and less work.
Kind regards,
Nicolas Busson.

How to Change the Document Condition Values in PO print

HI,
I have a requirement to change the document condition values in PO printout. We are using the copied form of MEDRUCK.
Please tell me how can i change the Document Condition Values at run time.
Thanks....

hi
hence you have copied standard script you cant able to change the driver program for this you have to use itcsy structure.
go to the page window and select the window which you have the amount field. open the text editor of the windoiw here write
/:           PERFORM CONTACT IN PROGRAM ZAMOUNT_ZF110_IN_AVIS1_C
/:           USING &REGUH-ZALDT&
/:           CHANGING &DT&
/:           ENDPERFORM
now create a report program with name ZAMOUNT_ZF110_IN_AVIS1_C.
and follow as the example program is .
*&      Form CONTACT
      text
     -->IN_TAB     text
     -->OUT_TAB    text
FORM contact TABLES in_tab STRUCTURE itcsy
                   out_tab STRUCTURE itcsy.
DATA : v_telf1 TYPE telf1.
DATA : v_telfx TYPE telfx.
DATA : v_adrnr TYPE ad_addrnum.
DATA : v_flagcomm6 TYPE ad_flgcm06.
DATA : v_datum(10) TYPE c.
DATA : v_sydatum TYPE sy-datum.
DATA : v_lifnr TYPE lifnr .         " Santosh Rawat , 19th Feb
DATA : v_email TYPE ad_smtpadr .   " Santosh Rawat , 19th Feb
LOOP AT in_tab.
    IF in_tab-name = 'REGUH-LIFNR'.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT' " Santosh Rawat , 19th Feb
        EXPORTING
          input = in_tab-value
        IMPORTING
          output = v_lifnr.
      SELECT SINGLE telf1 telfx adrnr FROM lfa1
        INTO (v_telf1, v_telfx, v_adrnr)
        WHERE lifnr = v_lifnr.
      SELECT SINGLE smtp_addr FROM adr6    " Santosh Rawat ,19th Feb
     INTO v_email WHERE ADDRNUMBER = v_adrnr. " Santosh Rawat ,19th Feb
     SELECT SINGLE flagcomm6 FROM adrc INTO v_flagcomm6
       WHERE addrnumber = v_adrnr.
    ELSEIF
      in_tab-name = 'REGUH-ZALDT' OR in_tab-name = 'REGUP-BLDAT'   .
      MOVE in_tab-value TO v_datum.
      REPLACE ALL OCCURRENCES OF '.' IN v_datum WITH ' '.
      CONDENSE v_datum.
      MOVE v_datum TO v_sydatum.
*CALL FUNCTION 'CONVERSION_EXIT_INVDT_INPUT'
EXPORTING
   input         = V_DATUM
IMPORTING
OUTPUT        = V_DATUM
      CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
        EXPORTING
          date_internal            = v_sydatum
        IMPORTING
          date_external            = v_datum
        EXCEPTIONS
          date_internal_is_invalid = 1
          OTHERS                   = 2.
      IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDIF.
ENDLOOP.
LOOP AT out_tab.
    IF out_tab-name = 'TEL'.
      MOVE v_telf1 TO out_tab-value.
    ELSEIF out_tab-name = 'FAX'.
      MOVE v_telfx TO out_tab-value.
    ELSEIF out_tab-name = 'EMAIL'.
      MOVE v_email TO out_tab-value.        " Santosh Rawat , 19th Feb
    ELSEIF out_tab-name = 'DT'.
      MOVE v_datum TO out_tab-value.
    ENDIF.
    MODIFY out_tab FROM out_tab.
*MODIFY TABLE OUT_TAB .
ENDLOOP.
ENDFORM.             }
reply for any query.
regards,
venkat.

PO - Change Condition pricing date

Can we change Condition pricing date in PO.If Yes , then How??
Thanx,
Viru

Dear Viru,
You can change the price date at the condition control tab. However, you still need to press
the update button from the condition tab to update the condition price follow the price date
that you had changed.
Best Regards,
Ian Wong

Function module to change the value for pricing condition type

Hello experts,
I want to change the value for pricing condition type for an item in the transaction CRMD_ORDER.
I used many function modules but none are working.
Please kindly suggest a function module that will change the value for a condition type .
I have used the following function module but its not working, please correct the coding if anything needs to be changed or added. Please help me .
Thank you.
CLEAR PRCD_COND.
     SELECT SINGLE * FROM PRCD_COND WHERE KPOSN = WA_ORDERADM_I-GUID AND
                                          KSCHL = COND_TY.
IF SY-SUBRC = 0.
*    MOVE-CORRESPONDING PRCD_COND TO L_COND_CHG.
*    CLEAR L_COND_CHG-KBETR.
    L_COND_CHG-STUNR = PRCD_COND-STUNR.
    L_COND_CHG-KBETR = COND_PRC.
*    L_COND_CHG-KSCHL = COND_TY.
    INSERT L_COND_CHG INTO TABLE T_COND_CHG.
L_HEAD_GUID = CRMD_ORDERADM_H-GUID.
L_ITEM_GUID = WA_ORDERADM_I-GUID.
INSERT L_HEAD_GUID INTO TABLE HEAD_GUID.
INSERT L_ITEM_GUID INTO TABLE ITEM_GUID.
    CALL FUNCTION 'CRM_ORDER_READ'
     EXPORTING
       IT_HEADER_GUID                    = HEAD_GUID
       IT_ITEM_GUID                      = ITEM_GUID
     IMPORTING
       ET_ORDERADM_H                     = LT_ORDERADM_H
       ET_ORDERADM_I                     = LT_ORDERADM_I
       ET_PRIDOC                         = IT_PRIDOC_RD
       ET_DOC_FLOW                       = T_DOC_FLOW
*     CHANGING
*       CV_LOG_HANDLE                     =
*     EXCEPTIONS
*       DOCUMENT_NOT_FOUND                = 1
*       ERROR_OCCURRED                    = 2
*       DOCUMENT_LOCKED                   = 3
*       NO_CHANGE_AUTHORITY               = 4
*       NO_DISPLAY_AUTHORITY              = 5
*       NO_CHANGE_ALLOWED                 = 6
*       OTHERS                            = 7
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRI_COND.
INSERT L_PRI_COND INTO TABLE PRI_COND.
LOOP AT IT_PRIDOC_RD INTO LS_PRIDOC_RD.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRIDOC_CHG.
L_PRIDOC_CHG-PRIC_COND = PRI_COND.
L_PRIDOC_CHG-REF_GUID = LS_PRIDOC_RD-GUID.
L_PRIDOC_CHG-COND_CHANGE = T_COND_CHG.
INSERT L_PRIDOC_CHG INTO TABLE PRIDOC_CHG.
ENDLOOP.
LOOP AT LT_ORDERADM_H INTO LS_ORDERADM_H .
MOVE-CORRESPONDING LS_ORDERADM_H TO L_HEADER.
INSERT L_HEADER INTO TABLE HEADER.
ENDLOOP.
LOOP AT LT_ORDERADM_I INTO LS_ORDERADM_I.
MOVE-CORRESPONDING LS_ORDERADM_I TO L_ITEM.
INSERT L_ITEM INTO TABLE ITEM.
ENDLOOP.
L_FIELD-FIELDNAME = 'STUNR'.
INSERT L_FIELD INTO TABLE FIELD.
L_FIELD-FIELDNAME = 'KBETR'.
L_FIELD-CHANGEABLE = 'X'.
INSERT L_FIELD INTO TABLE FIELD.
L_INPUT-FIELD_NAMES = FIELD.
L_INPUT-REF_KIND = 'E'.
L_INPUT-REF_GUID = LS_PRIDOC_RD-GUID.
L_INPUT-OBJECTNAME = 'PRIDOC'.
INSERT L_INPUT INTO TABLE INPUT.
    CALL FUNCTION 'CRM_ORDER_MAINTAIN'
     EXPORTING
       IT_PRIDOC                     = PRIDOC_CHG
     IMPORTING
       ET_EXCEPTION                  = EXCEPT
     CHANGING
       CT_INPUT_FIELDS               = INPUT.
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
REFRESH EXCEPT.
CALL FUNCTION 'CRM_ORDER_SAVE'
EXPORTING
    IT_OBJECTS_TO_SAVE         = HEAD_GUID
*   IV_UPDATE_TASK_LOCAL       = FALSE
*   IV_SAVE_FRAME_LOG          = FALSE
*   IV_NO_BDOC_SEND            = FALSE
*   IT_ACTIVE_SWITCH           =
IMPORTING
   ET_SAVED_OBJECTS           = SAVED
   ET_EXCEPTION               = EXCEPT
   ET_OBJECTS_NOT_SAVED       = UNSAVED
* CHANGING
*   CV_LOG_HANDLE              =
* EXCEPTIONS
*   DOCUMENT_NOT_SAVED         = 1
*   OTHERS                     = 2
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK AND WAIT.

Hi,,
To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to Update with immediate start
Alternatively u can use this function module.
CRM_STATUS_DATA_SAVE_DB
BAPI_CUSTOMERCRM_CHANGE (If u wish to use a bapi for this).
Also , Let me know what error you got when implementing other function module.Does the function module didnt return any error but still the value is not changed for pricing condition type?

Change value of condition in SD pricing procedure

Dear All,
I have requirement to change value of condition type in SD pricing procedure. Example: the value calculated by SAP in pricing procedure (up to the step) is 123, but i want to change this value to 100 sothat the next step in pricing procedure can use this value (i mean 100). Please let me know how to do this. Does routine in SAP solve this.
Thanks,

Thanks for your reply. However, I try to assign some exist routines, I failed to get value of condition ( I mean, the value until that condition). Maybe I need to make clear my question:
My pricing procedure will be like this:
10 PR00--->value 100.
20 ZDST---> discount 10%
30 get value from step 10-20 --->result is 90.
My requirement is: I want to change the value 90 to 2000 by my routine.
Pls give me your advice.
Thanks

"Conditions" button at the material master - Change the related condition

There is "Conditions" button at the material master ("Sales: sales org. 1" tab). We can make condition record of PR00 by this button but at our system the condition for the material price is different (it isZPR0 at our system). How can I change the related condition type as ZPR0 for this button?
Thanks in advance for the answers....

Check program LMGMMF0Q and FUNCTION SD_COND_GET_DEFAULT_CONDITION for details.
It looks it is hard coded, but they also mention that Via a user exit (business transaction event), the
default KSCHL and KOTABNR can be set.
Regards,

SV004 - I need to change the selection condition in the view: J_1BT001W

Hello guys,
Can you please help me with a topic ?
How can I change the selection condition in the view: J_1BT001W ?
I was trying to use se11, but says that J_1BT001W does not exist.
Thanks a lot,
Jordan

Hi Jordan,
The correct view name is J_1BT001WV and not J_1BT001W. It is made of table joins - T001W T001K T005. Please let me know if this answers your question.
Regards
Ram

PO to SO IDoc change (ORDCHG) - Extra condition pricing line generated. Why?

Similar Messages

Maybe you are looking for