BADI for Me21N - Condition types

Hi All,
wat ever condition type given in the header should be copied to all the items in the item level. then they want to change the condition type at item level for one or two items rest all are same like header condition types.
see we have a condition type optioned as header as well as item condition type So I have given this condition type in the header of PO . It will be automatically copied to all the items in the item level
right
Now for a selected item like let suppose third item i want to delete one condition type and want to give a new one for this it is not allowing me
Is there Any BAdI / Screen Exits which will allow me to copy the header condition type to all the items in Me21N and also it should allow me to Delete or modify that in the Item level
Awaits for the reply .......................
Its a high priority ticket
Pls Respond
Thnx in Advance
Regards
KAMAL

Hi Kaml ,
have u checked with ur functional pplz abt the possibility of doing it thru Config ?, i think they can do some value addition in this .
if you want to access those condition data u can try in these user exits but i'm not sure whether they can help u out in this requirement.
SPRO->MM-->Purchasing >Conditions->Enhancements.
regards
Prabhu

Similar Messages

ME21N : Donu2019t copy the price for all condition types from last po

Dear.
When I create a purchase order the price for all condition types are copied from last purchase order inside the info-record.
But I have some condition types like FRA1 or FRA2 that I donu2019t want that system transfer price from last purchase order.
How can I do that ?
Thanks.

Hi Cris,
Go to SPRO>MM>PUR>Info Record>Define Price History> Here with your Purchasing organization if the tick is active that
Specifies that the order price history (PO price history) is to be updated with the effective price.
Normally, the order price history is updated with the net price.
Procedure
Set this indicator if you want the order price history to be updated with the effective price.
Thanks
Diwakar

User Exit or BADI for ME21N

Hi All,
We are in a situation where in we need to Change the Distribution Channel in the Shipping tab of ME21N transaction.
Previously, the distribution channel is being picked up form the config (SPRO - Shipping data for plant) but before it picks up from the config we need to change it and update the other distribution channel in the PO.
We have tried with most of the User exits and BADIs but all of those are of no use for our requirement, as these user exits and badis are triggered after we click on save button. But we need to change the Distribution channel at the point of determination of Shipping data by the system i.e. before save.
Can any one please help me out with this situation with some User exits or BADIs that are triggered before save button.
Note: The Shipping data is in EKPV table. We need to change the VTWEG field in EKPV.
Thanks in Advance,
Asif Ali Khan

Asif,
see these are Exits and BADI for ME21n,
Enhancement/ Business Add-in            Description
Enhancement
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
MM06E001                                User exits for EDI inbound and outbound purchasing documents
MM06E003                                Number range and document number
MM06E004                                Control import data screens in purchase order
MM06E005                                Customer fields in purchasing document
MM06E007                                Change document for requisitions upon conversion into PO
MM06E008                                Monitoring of contr. target value in case of release orders
MM06E009                                Relevant texts for "Texts exist" indicator
MM06E010                                Field selection for vendor address
MMAL0001                                ALE source list distribution: Outbound processing
MMAL0002                                ALE source list distribution: Inbound processing
MMAL0003                                ALE purcasing info record distribution: Outbound processing
MMAL0004                                ALE purchasing info record distribution: Inbound processing
MMDA0001                                Default delivery addresses
MMFAB001                                User exit for generation of release order
MRFLB001                                Control Items for Contract Release Order
LMEKO001                                Extend communications structure KOMK for pricing
LMEKO002                                Extend communications structure KOMP for pricing
MM06E011                                Activate PReq Block
AMPL0001                                User subscreen for additional data on AMPL
LMEDR001                                Enhancements to print program
LMELA002                                Adopt batch no. from shipping notification when posting a GR
LMELA010                                Inbound shipping notification: Transfer item data from IDOC
LMEQR001                                User exit for source determination
LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001                                Customer-Specific Source Determination in Retail
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
M06B0003                                Number range and document number
M06B0002                                Changes to comm. structure for purchase requisition release
M06B0001                                Role determination for purchase requisition release
Business Add-in
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
ME_PO_PRICING                           Enhancements to Price Determination: Internal
ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001                           Control Items for Contract Release Order
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_REQ_POSTED                           Purchase Requisition Posted
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_BSART_DET                            Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN                    Commitment for return item
ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CHECK_OA                             Check BAdI for Contracts
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
Amit.

Badi for ME21N & ME22N to check storage location

Hello Guru's,
I need BADI for ME21N & ME22N to check storage location is maintained for plant used in PO i'm using method IF_EX_ME_PURCHDOC_POSTED~POSTED with definition name ME_PURCHDOC_POSTED but this throws message on SAVE.
But my requirement this message should be displayed before saving.Please guide

Hi,
Use BADI:
ME_PROCESS_PO_CUST
BADI CL_ME_PO_CUST
Business Add-in
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                      Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV                              BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST                    Enhancements to Price Determination: Customer
ME_PO_PRICING                              Enhancements to Price Determination: Internal
ME_INFOREC_SEND                        Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO                                  Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                           Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK               FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
ME_DEFINE_CALCTYPE                  Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C            Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001                           Control Items for Contract Release Order
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_REQ_POSTED                           Purchase Requisition Posted
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_BSART_DET                            Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN                    Commitment for return item
ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CHECK_OA                             Check BAdI for Contracts
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
Edited by: Neenu Jose on Nov 21, 2008 6:13 AM
Edited by: Neenu Jose on Nov 21, 2008 6:16 AM

In sales order for the condition type MWST, **Tax code** is displaying wron

Hi
In sales order for the condition type MWST, *Tax code* is displaying wrongly at header level i.e. FF instead of AO (under account determination tab)
AO tax is 0% but for FF it is 19%
I have checked with the Access sequence it is picking access 08 correctly according to this it should show AO in tax code field for MWST but it is not so..
There is a manual change for tax classification for material master in va02 initially it was blank now it is changed to ' 0 ' is any way influencing....?
Even if I consider material tax classification and customer tax code should not be FF because tax code FF is not maintained for the combination of access sequences for condition type MWST
Please help me.
Rajendra Prasad

Dear Rajendra,
There is a manual change for tax classification for material master in va02 initially it was blank now it is changed to ' 0 ' is any way influencing....?
Definitely material Tax classification will influence to determine the Tax code.
-->So Make sure that customer and material master having proper tax classification indicator.
-->Have you Update the price after changing the tax classification in the sales order.by going to item dat -->condition tab then click on Update push button bottom of the conditions screen.
-->Once again the check the condition record maintanence also for your MWST access sequence.
I hope this will help you,
Regards,
Murali.

Tax not calculated in MIRO for the condition type JVCD

Hi,
We made some new different tax code and attached with JVCD , its calculating in PO but in MIRO calculation part not done but for other condition type ,JVRD,JVRN system calculating well...
Please tell me some way why not system calculating in case of JVCD and JVCN for capital case..
Thanks in Advance,
Dharmveer

Hi,
We totally agreed with you and already we checked our configuration part is OK.Actually we want to map some process where we captured excise in GR but no need to take credit i.e. to post the excise in J1IEX,so we do not have to post our cenvat/modvat entry in MIRO but we need to calculate VAT whether it is deductible or non deductible.So far this thing is concerned,we made separate tax code which we use at time of MIRO posting and in configuration we did not attached the tax code in logitics-basic excise -assign to company code. Because once we attached here , system asking to make to pass furst RG part2 entry then it allows to post MIRO entry which we do not want .So please understand this scenario is different and we got the success for JVRN/JVRD for VAT but getting issue in case of capital VAT where system does not calculate tax for JVCN/JVCD .....where we want to process MIRO without posting J1IEX..
Please thing and analyse ..give some helping response..
Thanks,
Dharmveer

New Tax code Creation for CST(Condition type

Hi Friends,
I am facing an issue during creation of new Tax-code for CST; condition type JIN1. After defining the tax percentage; system is picking an automatic G/L account, which is a grey field and can't be editable. We need to change G/L account and need to assign a new one.
Can you please tell us how can we remove the default assigned and non-editable G/L account.
Your support is appreciable.
Rgds, Krishan Raheja.

Hi Krishnan,
Use transaction OB40, here double click on the Account Key (you can check this account key assigned to condition type in OBQ3 and also in FTXP screen) that is mapped to condition type JIN1 and enter your chart of accounts. Now change the G/L account you want.
Regards,
Chintan Joshi.

Function Module for getting the Sales Price for a condition type

Hi,
I am looking for a standard function module to which I can pass my condition type(new customizing) and it will return the sales price. The customer is going to create some new condition type to manitain the sales price. I'll have the necessary information like material/sales org/distribution channel, customer and need the standard function module to read the condition records for that condition type(as configured) and give me the price. PLease help if you know of a standard function module performing this.
Thanks in advance.
Regards
Malthi

Hi malthi ,
welcome to sdn
for material sales area u can look for the validations is table MVKE.
the classification of the conditions is in tables like A901, a902 etc which in my opinion holds the condition types per classification .
put a A* in se11 and this will give the list of tables per classification .
u need to get the conditions as per kschl and dmbtr and
etc..
like this ..
Get Condition Values for Material/Plant combination
IF NOT i_a916[] IS INITIAL.
    SELECT knumh kappl kschl krech
           kbetr konwa kpein kmein
           INTO TABLE i_konp
           FROM konp
           FOR ALL ENTRIES IN i_a916
           WHERE knumh EQ i_a916-knumh AND
                 kappl EQ i_a916-kappl AND
                 kschl EQ i_a916-kschl AND
                 loevm_ko NE 'X'.
ENDIF.
Get Condition Values for Material/Plant/Ordertype/
Customer combination
IF NOT i_a925[] IS INITIAL.
    SELECT knumh kappl kschl krech
           kbetr konwa kpein kmein
           APPENDING TABLE i_konp
           FROM konp
           FOR ALL ENTRIES IN i_a925
           WHERE knumh EQ i_a925-knumh AND
                 kappl EQ i_a925-kappl AND
                 kschl EQ i_a925-kschl AND
                 loevm_ko NE 'X'.
ENDIF.
just check this Fm if u can apply ur condition over here ..
ME_GET_PRICE_CONDITION
regards,
VIjay.

Condition Records For Tax Condition types for SAP 4.7

Dear Experts,
What is the procedure to maintain condition records for tax condition types like CST , VAT and Service Tax. We are not using CIN. In MM01 and XD02 tax classifications i have maintained UTXJ condition Type and also maintained the above mention tax condition types.. But when i create condition records for UTXJ in VK11 the sysytem is asking for Tax code. In FTXP when i defined Tax code A1 for Tax ProcedureTAXIN1 where i maintained all the Tax condition types there.But i am unable to save the Tax % in FTXP.When i try to save the tax code it is not saving.
Is there any other procedure to maintain Tax condition types for SAP4.7.
My Pricing procedure that i maintained in V/08 is Z00001.
Regards
Jyoti

Hi Jyoti
Since you are not using CIN, you can do the follwing for tax conditions
Check the assignment of the TAx procedure to country
once u do this , you will be able to maintin the vendor and customer records for MWST type for taxes
then create condition records for MWSt with access sequence MWST in condiution type or design one suited to your needs
alternatevely in the current procedure you can change access sequence for condition type UTXJ form the current one to MWST and then maintain condition records
hope this helps
thanks
Akasha

Tax value is not picked up correctly for the condition type in SO creation

Hi All,
I have a issue in Picking up Tax value correctly for the condition type in SO Creation.
Actual Issue:
When creating the sales order manually,
tax value is picked up correctly for one condition type: ISS3.
When the Sales Order is created via Idoc using the function module 'idoc_input_orders', tax value is not picked for same condition type: ISS3.
We need to find out why the value for the condition type 'ISS3' is not picked in this way!
Can anybody solve this issue!
What can be the reason which is stopping picking up tax value for condition type: ISS3 when Sales Order is created via F.M 'IDOC_INPUT_ORDERS'! While it picked up the same while creating Sales Order manuallly.
Thanks in advance.
Thanks,
Deep.

Hi All,
Can anybody give the solution for above posted issue!
Working:
When creating the sales order manually,
tax value is picked up correctly for the condition type ISS3.
Actual Issue:
When the Order is created via Idoc using the function module 'idoc_input_orders',
tax value is not picked .
I need to find out why the value for the condition type 'ISS3' is not picked.
I have debugged the issue from WE19 but upto Conditions tab it is picking up tax value but then it is becoming zero again it remains zero after saving SO.
But Manually tax value is picked up for condition type ISS3 and remains same after saving order.
I have debugged it several times fro WE19 but not able to find route cause for the issue.
What can be the issue over here!
Can anybody give me solution for the same!
Thanks in advance.
Thanks,
Deep.

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?

Badi for me21n,me22n,me23n

HI experts,
CAn any one help me out infinding a badi for me21n,me22n,me23n, which triggered on every press of enter key or some other check, so that i could kept a validation for the header and item fields of the t.codes

Hi,
Go for BADI,
Follow the below steps to find out what all BADI's are called when you press any button in any transaction.
1) Goto se24 (Display class cl_exithandler)
2) Double click on the method GET_INSTANCE.
3) Put a break point at Line no.25 (CASE sy-subrc).
Now
4) Execute SAP standard transaction
5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
7) This way you will find all the BADIs called on click of any button in any transaction.
Reward points if useful....
Regards
AK

Hide values for certain condition types in Quotation Saleorder and Invoice

Hi All,
I have written code to hide values for certain condition types in LV69AFZZ,
this works fine in the ITEM LEVEL.
But for the same condition types, I could not hide the values in the HEADER LEVEL.
Unless I hide it at header level also, this is useless.
Please guide me how to do it.
Thanks & Regards
Pradeep

Hi,
We have been using FORM USEREXIT_FIELD_MODIFICATION of LV69AFZz for item level & FORM USEREXIT_FIELD_MODIFIC_KOPF of LV69AFZZ for hiding heade level conditions.
I hope this helps,
Regards
Raju chiutale.

Authorization object for manual condition type in sale order

Hi experts
I want ask them, If exist an authorization object for manual Condition type (KOMV-KSCHL) in the sales order (VA01/VA02), that the user don' t can create neither modify the sale orden with a specific manual condition type (payment term) by stardard way.
Best regards
John Angulo

HI John,
I would be surprised to know that someone uses the Payment terms as a condition in the Pricing procedure for sales orders. The payment terms define when the customer agrees to pay, (15, 20, 45 ,....days or 5 years or 10 years....whatever it be)
this detail for what i know is in the sales order header,and ideally has nothing to do with the Item level material price conditions.
its ok, If you mean something else by payment terms.....in principle you can have a conditon type restrcited such that manual entries on the condition are not possible. this cane be done in SPRO customizing, i am sure your functional consultants would know what to do (SPRO->Sales and Distribution->Basic Function->Condition Types), in the tab "Changes that can be made" have a value that says manual Processing is not allwowed
The ABAP route mentioned above is for a different scenarion and i dont think it is necessary for your requirement

How can we create new pricing requirement for a condition type

Hi All,
I am in urgent need of creating new pricing requirements for a condition type.
Or if there is already a conditin type existing and we want to make changes in the pricing requirements of that condition type, How can we do so ?
In short if you can let me know how does pricing get impacted by the condition types.
Thanks
Mark

Hi!
The common transactions for condition mantaining are VK11, VK12, VK13.
In SPRO - Sales and distributoin - Basic function - Pricing - Pricing control - *.
Is this what you want?
Regards
Tamá

BADI for Me21N - Condition types

Similar Messages

Maybe you are looking for