User Exit or BADI to update table PSPR_GRP_IND in CJ20N t-code

Hi All,
I have a requirement to update values in tab Collective PR indicator i.e. field GRP_IND in table PSPR_GRP_IND while saving a project using transaction CJ20N on project definition level.
But I am unable to find relevant user-exit or BADI; please let me know if anybody has worked on such a requirement and if so then what user-exit or BADI was used or if there is some other solution.
Thanks in advance!
Regards,
Swapnil.
Edited by: Swapnil Sharma on Jul 30, 2010 9:35 AM

Hi,
I have worked on CJ20N Transaction but the Tab Collective PR indicator I am not able to see in CJ20N.
I have used EXIT_SAPLEBND_001 Exit for my requirement.
Regard's
Shabbir

Similar Messages

User Exit or BADI for Updating Tax code (MWSKZ) using ME21N

Hi all,
I am trying to fin out an exit or badi for Updating Tax code (MWSKZ) and Unit of Measure in transaction ME21n.
The scenario is like this...
For Purchase Orders Tax code will be defaulted from Purchasing info record or contract or parameter id for that item-vendor-plant.
If the Tax Code is not defaulted and account assignment is blank then tax code on the PO is updated according to the below mentioned table
Table
Supplying Plant/              Receiving Plant                      Tax code
Vendor/Country
Any plant/vendor/
country                           5050(NA)                               20
2300                              6700                                     E0
If the tax code on PO cannot be updated by the above table, then buyer needs to put tax code on the purchase order manually.
Thanks,
Shiva, Bangalore

Hi Siva.,.,.,
These r the exits.,..,which will be called while calling ME21N/ME22N/ME23N
EXIT_SAPMM06E_006
EXIT_SAPMM06E_007
EXIT_SAPMM06E_008
EXIT_SAPMM06E_009
EXIT_SAPMM06E_012
EXIT_SAPMM06E_013
EXIT_SAPMM06E_014
EXIT_SAPMM06E_016
EXIT_SAPMM06E_017
EXIT_SAPMM06E_018
U want to default some values while the Initial screen will come right,
while u Enter ME21N in command Prompt.,.,two exits will get triggerd,
EXIT_SAPMM06E_014
EXIT_SAPMM06E_016
If u want to Default some values u can use these two exits.,.
Try using EXIT_SAPMM06E_016.,.this will solve ur purpose.
and if the user changes some values on screen.,,and you want them to get reflected .,.,.that means if user changes and saves data .,.
While saving.,.,EXIT_SAPMM06E_012 and EXIT_SAPMM06E_013 will get triggerd
Try using EXIT_SAPMM06E_013.,,.it was somehow the same requirement as mine.,.,IN my case it worked fine.,.,
Regards
Debasish
Message was edited by:
        Debasish Das

User Exit or BADI to update the service order in R/3

Hi,
When creating a service order the following fields need to be populated automatically using an user exit or badi.
1. Planner Group
2. PMActType Plant maintenance activity type
3. Cost/Profit Centre
4. WBS element
5. Work center
so my requirement is there any function module or Badi or user exit to update the service order details when service order is created / changed.
Pls do the needful.
Reg
Ramana

Hi Ramana,
Go to SPRO Transaction and follow the below path
Customer relationship management>Transactions>Settings for Service Processes>Business Add-Ins and you will find 8 BADI's.
Check these BADI's useful for you.
Regards,
Lijo Joseph

User Exit or BADI to update the service order

hi,
When creating a service order the following fields need to be populated automatically using an user exit or badi.
1.     Planner Group
2.     PMActType Plant maintenance activity type
3.     Cost/Profit Centre
4.     WBS element
5.     Work center
so my requirement is there any function module or Badi or user exit to update the service order details when service order is created / changed.
Pls do the needful.
Reg
Ram
Message was edited by:
        RAMANA MYLAPALLI

Best Possible way is.
go to se24 -> type in CL_EXITHANDLER -> Go to get_instance method.
Put a breakpoint on CALL METHOD cl_exithandler=>get_class_name_by_interface.
Now run the transaction and check which all BADI and user exits are invoked when u call the transaction.
Idenitfy the BADI which can be useful to you.
Reward if u find it useful.
Thanks
Kartavya

USER EXIT or BADI to update the field in trx. ME41

Hi guys,
My requeriments is update the field EKKO SUBMI of record when the trx. ME41 but can not find how to do it, the BADI ME_PROCESS_CUST the method POST not allowed me to meet user and not allow the update the field.
Please help ...
Thanks.

Hi Ramana,
Go to SPRO Transaction and follow the below path
Customer relationship management>Transactions>Settings for Service Processes>Business Add-Ins and you will find 8 BADI's.
Check these BADI's useful for you.
Regards,
Lijo Joseph

Need to find appropriate User Exit for VL04 for updating table LIKP

Hi Gurus,
I need to create split Deliveries using Transaction VL04. I have a custom field ZZINCOLOC (location) in table VBAP.
The requirement is that when ever a sales order Line Item values for ZZINCOLOC differs, that is if Item 10 has value 1234 for ZZINCOLOC and then if Item 20 has value '4567' in ZZINCOLOC then 2 deliveries should be created through transaction VL04. I also need to add this custom field ZZINCOLOC in LIKP table (delivery Header). Now when the 2 deliveries are created , in the 1st delivery LIKP-ZZINCOLOC should be updated with VBAP-ZZINCOLOC where Item is 10 and when 2nd delivery is getting created, LIKP-ZZINCOLOC should be updated with VBAP-ZZINCOLOC where Item is 20.
Can anyone tell me how to do this. Where to write the code.
Thanks and Regards,
Nabanita.

hi
Check this BADI - BADI_CUST_HIER
Hope this helps

User exit or badi for transaction code CORS

Hi All
I am looking for user exit or badi to update item text while executing transcation code CORS.
Please Advice
Thank You
Ravindra Suvarna

Hi
Check these enhancements and exits
CONFPS05 PS confirmation: Customer specific enhancements when saving
EXIT_SAPLCORF_010 PS Confirmation: Customer-Specific Enhancements when Saving
CONF0001 Enhancements in order confirmation
EXIT_SAPLCORU_001 Order Confirmation: Deactivation of Functions

User exit or BAdi for field update in ECC system for SUS supplier

Dear Guru's,
I am configuring MM-SUS scenario in our srm 7.01 scenario. Not all vendors of our client are going to be SUS vendors. For SUS vendors, the client will be using Purchase Order Acknowledgement and Advanced Shipping Notification key. I am thinking of configuring a confirmation control key which will incoporate requirement of PO acknowledgement and Inbound delivery document. The assignment of confirmation control key and PO Acknowledgement Required checkbox in the vendor master record will default it in the purchase order.
Now, the question is how to update the existing vendor master data record which will be SUS vendor. I am looking at a solution like user exit or BAdi which updates the confirmation control key and purchase order acknowledgement required check box when the client manually assigns the class 'Z_CRED_SUSMM' to the ERMS vendor master.
Could you please help me to find the required exit or BAdi?
Thanks and regards,
Ranjan
Ranjan Sutradhar

EXIT_SAPMF02K_001 definitely wont work as this is for custom checks. this does not update data in vendor master.
you can try using below method of VENDOR_ADD_DATA badi.
IF_EX_VENDOR_ADD_DATA~PRESET_VALUES_PORG
but you need to read the screen field for classification and then according to that i think you can change the LFM1 data inside this badi

Need exit or Badi for updating Warranty data in IE02 while Prod Order conf.

Hi All,
I need a user exit or Badi for updating the Warranty data in IE02(Equipment Master) while production order confirmation(CO15)?
I need to update the Begin guarantee date from Production order and warranty master type in IE02 while confirming the production order.
Thanks,
Sudha

Hi,
Are you saying first create notification,then service order
and then Sales order.
But the requirement is create notification then sales order and when you go in va02 and while modifying the sales order and create service order.
Thanks & regards,
chetan.

User-Exit or BADI required for F-28

Hi All,
Can anyone give me any user-exit or BADI to update BSAD-VBELN when posting open items using txn F-28.
regards
Ajay

Hi,
Use BTE 1120 for this. But when you clear open items and you clear more than one invoice line items in one go.. then it will create issue.
We had used this once but we had restriced by way of code that not more than one RV document can be selected and this worked..
Regards,
SAPFICO.

User exit or BADI for MIGO to Update a field in MSEG-KOSTL

Hi,
I want to update/change the KOSTL (Cost center) value before creating/posting the document.
Please let me know is there any user exits or BADI, which will export the MSEG structure.
Regards,
Ganesh

Hi
I believe there isn't a BADI or EXIT allows to change item data, I usually use the exit to change the item text EXIT_SAPMM07M_001 (the BADI MB_MIGO_ITEM_BADI should be the same thing) where I change the data by field-symbols:
FIELD-SYMBOLS: <KOSTL> TYPE MSEG-KOSTL.
ASSIGN '(SAPMM07M)MSEG-KOSTL' TO <KOSTL>.
<KOSTL> = .......
Max

Badi or user exit to uncheck Info-update checkbox

Hi guys,
How can I uncheck by code the Info-update checkbox for one type of purchase order?
I need one user exit or Badi to do this, so any suggestion?
Thanks in advance.

Use BADI ME_PROCESS_PO_CUST.
As info-update checkbox is located at item level, you need to use PROCESS_ITEM method of this BADI.
G@urav.

User exit or BADI for recruitment

Hi,
I am new to HCM, can you give me user exit or badi for recruitment.
Requirement - i have developed an infotype which i am updating through BSP, while the custom infotype is updated it should simultaneously update some of my Z tables. Hoping for positve replies earliest.
Thanks in advance:-
Santosh

Hi,
InfotypeThe data fields of HR master data, time management and recruitment are grouped logically into information types or infotypes for short.
Examples of infotypes are "Family/Related Person", "Organizational Assignment, "Basic Pay".
The following naming conventions apply to infotypes:
Infotypes 0000 to 0999 are used for HR master data
and sometimes for applicant data
Infotypes 1000 - 1999 for organizational management
Infotypes 2000 - 2999 for time data
Infotypes 4000 - 4999 for applicant data
Infotypes 9000 - 9999 for customers
Function character of step
This controls for which types of processing (create, change and/or delete a data record) a dynamic action should be carried out.
The processing type is indicated by a two-digit numeric value. These values can be added up; in other words, you can enter several processing types for each infotype, subtype or field. A dynamic action can also be carried out independent of the current processing type.
00 for Independent of the current function carried out
02 for Change
04 for Create
06 for Change and create
08 for Delete
10 for Change and delete
12 for Create and delete
Examples
If you enter 06, an action is carried out if the specified infotype was created or changed.
If you enter 00, an action is carried out irrespective of whether the specified infotype was created, changed or deleted.
Variable function part
The variable function part, which depends on the indicator for step, can have the following meaning:
P - Plausibility checks
You can enter values for specific infotype fields. Field names must be entered in full. Literals and constants can serve as comparison values. These must be enclosed by inverted commas. Variables can also be used.
The old value of a field can be used for comparison; the field name must be preceded by PSAVE-.
If fields of other infotypes are used for comparison, these must be stored in the module pool of the current infotype.
The following comparison operators are supported:
= equal to,
< less than,
<= less than or equal to,
> greater than
>= greater than or equal to and
<> not equal to.
Consecutive checks must be linked by a logical AND. Logical OR links must also be indicated by a /X.
Note:
Note that all checks with OR links must have a /X.
If the result of the comparison operation is not "true", then the following commands (I, F, W etc.) are skipped over until a field is reached or a new comparison operation takes place.
Examples
Infotype Field ..... Ind. Variable function part
0007 STAT3 P P0007-STAT3='0'
0007 STAT3 P PSAVE-STAT3='1'
The step is taken if the value in the P0007-STAT3 field changes from 1 to 0.
0007 P P0013-KLKZ1<>'0'/X
0007 P P0013-ALVKZ<>'0'/X
0007 P P0013-RVKZ1<>'0'/X
0007 P P0013-RVNUM=SPACE
The first three conditions are linked by an OR; at least one of these conditions must be met. Condition 4 must always be met.
The step is taken if the following holds true:
P0013-KVKZ1 not equal to 0 or P0013-ALVKZ not equal to 0 or P0013-RVKZ1 not equal to 0, and P0013-RVNUM empty.
I - Maintain infotype record
Enter the step, infotype, subtype, object ID, start and end dates of the record and an indicator which defines whether the step is to be run in the background. The possible actions are INS, COP, MOD, and DEL.
Use commas to separate selection criteria just like the separator in the matchcode. If an entry is missing, the system inserts a comma.
Separate the indicator for suppressing dialog from other entries by a slash D (/D).
Constants, such as those for subtypes, are not enclosed in inverted commas.
Variable entries are also permitted. Fields containing such values must be put in brackets.
Examples:
Infotype Field .... Ind. Variable function part
 .... I INS,19,01/D
Step: Create a Dates record, subtype 01, run in the background
 .... I DEL,14,M559
Step: Delete Rec. Payments/Deds. record with subtype (wage type) M559.
0007 .... I INS,8,,,(P0007-BEGDA),(P0007-ENDDA)
Step: Create a Basic Pay record (0008) without subtype and object ID. The start and end dates are the same as those in the current Planned Working Time record (0007); specify these two fields only if they are filled because the dynamic action was triggered by this infotype.
W - Default values for new record
Literals or variables are used as default values.
Set the defaults for the infotype, subtype, object ID, start and end dates using an I step and not a W step.
Do not set defaults for Q fields of an infotype because the values for these fields are derived from the corresponding P fields.
Examples
Infotype Subtype ..... FC Ind. Variable function part
0021 2 04 I INS,0015,M430
0021 2 04 W P0015-BETRG='10000'
When a Family/Related Person record (0021) record with subtype 2 (child) is created, an Additional Payments record (0015) with a default amount of 100.00 is created.
V - Cross-reference to another step
Here, you can combine fields to groups. The variable function part contains the value in the field which follows the "field" column. Steps which are specified only for the following field are also triggered for each of the other fields.
Examples
Infotype Field ..... FC Ind. Variable function part
0016 PRBZH 06 V PRBZT
0016 PRBZT 06 I DEL,0019,01/D
Infotype 0019, subtype 01 is deleted in the background when the field PRBZT or PRBZH in infotype 0016 is changed or created (function code 06).
The following entries are equivalent:
0016 PRBZH 06 I DEL,0019,01/D
0016 PRBZT 06 I DEL,0019,01/D
F - Call a routine
You can call internal (module pool) as well as external routines.
If you call external routines, type the program name in brackets after the routine name. Do not specify 'using' parameters. When calling an external routine, all data must be declared in a common part. You can use the fields of structure RP50D to return values from the routine. These are not used in the standard system and can only be populated via the routine and then can be used for defaults (W-Commands).
This allows customer-specific routines to be formulated with all the above steps.
Example 1:
Infotype Field ..... Ind. Var.function part
0016 PRBZT F PROBATION
0016 PRBZT I INS,19,01
0016 PRBZT W P0019-VTRMN=PRBEND
Module pool MP001600 contains the PROBATION routine. This routine uses the entries in the fields P0016-PRBZT and P0016-PRBEH to determine the end of the probation period which it stores in the field PRBEND.
The system creates a new 'Dates' record with the reminder date = PRBEND.
Example 2:
Infotyp ..... Ind. Var. function part
0001 F GET_DATE(ZPUDYN01)
0001 I INS,19,01
0001 W P0019-VTRMN=RP50D-DATE1
The GET_DATE routine in program ZPUDYN01 calculates a date and enters this date in the RP50D-DATE1 field via "TABLES RP50D" in ZPUDYN01. This date can be user-defined in GET_DATE: if necessary, user-defined infotypes can be read afterwards.
M - Send a mail
Enter the name of the feature which defines the characteristics of the mail.
Example
Infotype Field ..... Ind. Var.function part
0001 SACHP M M0001
A mail is sent when the field SACHP is changed. The characteristics of the mail are defined in feature M0001.
In the standard system, feature M0001 is provided as a model. The documentation on feature M0001 explains how to define the characteristics of a mail.
ADDITIONAL HINTS
If you use a date as a constant, enter it as YYYYMMDD (YYYY=year, MM=month, DD=day).
The table strings T001P, T503 and PSPAR are filled with the values which are valid on the record start date.
The old values of the infotype are stored in the field string PSAVE. The structure of this string is the same as the Pnnnn structure (nnnn=infotype). The structure is filled with (valid) values only when the delete, change and create functions are used.
Please read Create dynamic actions in the Implementation Guide.
Regards
Bernd

User Exit or BADI for Blocking process orders from R/3 to APO?

Dear Experts,
I am looking for a user exit or badi to block the process orders from R/3 to APO. As per standard it is not transferring orders which are clsd(closed status). Means that it is not updating live cache but its reading from R3.
We are facing some problems in cif queues which are not correctly maintained in R3 side. We dont want to touch those orders bcoz its very old data which is not required for planning.
There will be huge data which needs to be deleted while transferring through cif.
Please give any user exit (outbound intial transfer) from R/3.
Or any sugg. I apprecite your inputs...
Thanks
Cris

Hi Cris,
You can use user exit APOCF004 - Inbound Processing: Production Order/Planned Order in APO to prevent orders coming to APO by deleting orders which are not intended to goto APO from internal tables IT_ORD and IT_OUT.
Hope this helps.
Best Regards,
Ramesh M

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.

User Exit or BADI to update table PSPR_GRP_IND in CJ20N t-code

Similar Messages

Maybe you are looking for