BADI deactivation in ECC6.0

Hi, I have a badi based on the definition 'ME_PROCESS_PO_CUST' in ECC6.0. I had to migrate it to the new enhancement point during our recent upgrade from 4.7. The BADI is called correctly and all our code contained within works well. However, when I deactivated it, which it did without an issue, it is still called from the SAP transaction in question, in this case ME21/2n. The enhancement implementation says it's inactive, the runtime behaviour tab says it's inactive however the badi is executed every time that part of the code is called. Does anyone know why this is happening?
Thanks,
Kevin

I solved this one on my own. In ECC6.0 it seems that in addition to deactivating your own implementation in SE19 it is also necessary to do the same in SE18 under the enhancement implementations.
Kevin

Similar Messages

Creation of BADI definition in ECC6.0

Experts,
How to create a custom badi in ECC6.0 and I want to implement with filter functionality as well.
How can I do that in ECC6.0? I have gone through some of the docs which I got from SDN itself.
But, those are not helpful to me.
Please help me....
Thanks in ADVANCE...
Sridhar.....

hello sridhar,
in ECC 6.0 u cant create BADI directly as in 4.7 ,
u have to create badi definition as part of enhancement spot
Either create an enhancement spot or process an enhancement spot that already exists. There you can create BAdI definitions as part of the enhancement spot, once created enhancement then u can add badi definition and then filter to it
regards
afzal

How can create badi in version ECC6.0

Hi All,
How can u crate Badi in ECC6.0.We r in Ecc6.o.Ofter giving SE18 and enter badi name and press create button.It will not accept to creat the badi instead of dey giving error(we have to create first enhancement spot).
Coupd any one help regarding this.
Thanks

Hello Anil,
In SE18 transaction try using the Menu Path
Utilities-Create Classic Badi
With Regards
Avisesh.

BADI's in ECC6

I need the documentation for developing a BADI for any example in ECC 6

Hi,
please have a look at
http://help.sap.com/saphelp_erp2005vp/helpdata/en/70/63da4023a28631e10000000a1550b0/frameset.htm
Hope this helps.
Regards
Bernd

Urgent regarding BADI deactivation From SPRO

Hi guru,
Can i have delete BADIs implemantaion using SPRO. please give the detail if possible then?
Reward if helpful.
Thanks and regards,
SAHIR

Hi,
The same issue occurs which could not generate method for New BADI implement or change method on original one when I test the cancel billing process,Maybe Autorization on 'S_DEVELOP' be taken into account, I still waiting IT support for the authority,
And open issue is that how to implement a Enhanment spot migrated from classical BAdI?
B.G

Am I correct to say there's no BAPI/BAdI for updating an MSEG extension ?

SAP allows you to append to MSEG in dictionary, although many customers agree this is not a good thing to do.
But suppose your customer has decided to extend MSEG.
As far as I can tell, SAP does not allow update of this extension via any of its BAPIs or BAdIs.
My reason for claiming this is that:
1) MSEG is received "importing", not changing, by the screen-handling interface IF_EX_MB_MIGO_BADI that allows you to put a custom tab on MIGO
2) MSEG is received "importing", not changing, by the standard MIGO update interface BAdI IF_EX_MB_DOCUMENT_BADI.
3) There are 79 flavors of Goods Movement BAPI, and so far as I can tell, none of them have "extension" capability (like the PR or PO BAPIs.)
Do you all agree that:
there is no way to update the custom portion of an MSEG record using an SAP provided BAPI or BAdI.
If you disagree, please point me to the BAdI or BAPI that does this.

Also, please note that extension capability, even in CREATE mode, is only available in a "new-style" BAdI, and therefore only at level ECC6 or above - this is spelled out specifically in Note 906314 - where it indicates that the BAdI is a "new-style" BAdI.
So at ECC5, there is no extension capability for MSEG in any BAPI or BAdI, and at ECC6, it is still an open question in my mind as to whether there is extension capability in change mode.

BADI FI_ITEMS_MENUE01 URGENT!!!!!!!!!!!!!!!!!!

We have implemented the above badi in <b>ECC6.0</b> to add a push button in <b>FBL5N</b> transaction and it is working fine in DEVLOPMENT server. We have transported the transport request to QUALITY. But we are not able to see the push button. The transport went fine to QUALITY. Can anyone tell us what the reason is?
Your help is greatly appreciated.

Hi Denis,
Check this Link for enhancing screen via BAdi,
http://help.sap.com/saphelp_47x200/helpdata/en/6a/8b14e2340d11d5b3ba0050dae02d7c/content.htm
http://www.allsaplinks.com/badi.html
And also download this file....
http://www.savefile.com/files.php?fid=8913854
There are other tutorials on this site...
http://sapbrain.com/Tutorials/tuto_download.html
Regards,
Ranjit Thakur.
Please Mark The Helpful Answer.

Migration of Standard Classic Badi to New Badi

hi,
Is it mandatory to migrate all standard classic badi's to New badi's in ECC6.0. I have read in the documentation only custom BADi's should be migrated.
Can we migrate Standard Classic badi's to New badi's, please provide the procedure for this.
when i am trying to do this in one way it is not allowing me to use the same class as classic badi used, so i have created custom class for this. Is it going to effect.

Hi Phanindra,
Calling New badi's is much faster than calling clasic badi's. SAP never recommends to convert all classic Badi's to New Badi's rather you convert your own Badi's to New Badi's. You cant convert SAP classical BADI to New Badi. if you want to convert custom Badi, then please go through this below link
http://help.sap.com/saphelp_nw70/helpdata/EN/0e/4d3e42fc94aa04e10000000a1550b0/content.htm
Thanks,
Bishnu Dash

Z implementation not getting picked for BADI - MB_DOCUMENT_BADI

Hi,
I have a done a z implemenatation for standard badi MB_DOCUMENT_BADI in ECC6.In Tcode MIIGO after giving 2 line items when i save it that Zimplemen is not getting picked.
In 4.6c the same Z implementation is getting picked.
can you please help me out in this.

Hi Rajeev,
I am not sure about the definition of Badi and hence am assuming that the filter is set....and the value for the z implementation does not match the value passed from the call point. Can you please check this and confirm
Regards,
Jemin

Add new field into result of the transaction MD4C

i want more information into the result of MD4C
example:
delivery date of the purchase order and confirmation date of the purchase order and field USR06 of PRPS table and other field like
moving average price VERPR of the table MBEW and other information from SAP table related to purchase order or WBS elements or Order
thanks a lot for reply
best regards
Patrice

User exits and BAdI's for MD4C
Enhancement/ Business Add-in            Description
Enhancement
CO610001               User exits: Assembly processing
M61X0001               User exits PP-MRP materials planning
M61X0002               User Exits PP-MRP Material Requirements Planning Evaluations
Business Add-in
MD_MRP_RUN_PARALLEL         Add-Ins for parallel planning run of requirements planning
MD_PIR_FLEX_CONS            BAdI for flexible planned ind. req. consumption/reduction
MD_PLANNING_RESULT          BADI for Issuing Planning Result
MD_PLANNING_SCENARIO          BAdI for Maintenance of Add. Parameters in Planning Scenario
MD_PLDORD_BOMEX_CIF         BAdI: Deactivation of BOM Forced Explosion in CIF
MD_PLDORD_CHANGE            BAdI for Changing Planned Orders
MD_PLDORD_POST              BAdI: Update of Planned Orders
MD_PLDORD_SCHEDULING          BAdI: Schedule Planned Orders
MD_PLDORD_TIME_STAMP          BADI for publishing time stamp problems
MD_PURREQ_CHANGE            BADI for changing purchase requisitions
MD_PURREQ_POST              BADI for updating purchase requisitions
MD_PURREQ_REL_STRAT         BAdI for Deactivating Release Strategy for MRP Purch. Reqs
MD_STOCK_TRANSFER           BADI: Change the Requirement Date During Stock Transfer
MD_SUBCONT_LOGIC            BADI: Determine Subcontracting Logic
MD_ADD_COL_EZPS             BAdI: Extra Columns for Evaluation PP-MRP Reqmnts Planning
MD_ADD_COL_OVERVIEW         BAdI: Display of Additional Columns in the Material Overview
MD_ADD_ELEMENTS             BAdI for Adding Additional Requirements/Receipts
MD_ALTERN_EXPLOSION         BAdI for Alternative Explosion of Planned Orders (IPPE)
MD_CHANGE_CALENDAR          BAdI: Change Calendar for Range of Coverage Calculation
MD_CHANGE_MRP_DATA          BAdI: Change Data when Importing MDPSX
MD_DISPLAY_ELEMENT          BAdI for Changing Display of MRP Elements
MD_EXT_SUP                  BAdI for Determining the Issuing Storage Location
MD_INTERACT_PLANNING          BAdI for Deactivating Changeability of MRP Elements
MD_LAST_LOT_EXACT           BAdI for Calculating Last Lot Exactly in Individual Segment
MD_MODIFY_PRODVERS          BAdI for Modifying Production Version
MD_MODIFY_SOURCE            BAdI for Modifying Source Determination in MRP
MD_MRP_LIST          BADI for further processing of MRP list
MD_MRP_PARAMETERS           BAdI: Change Planning Parameters

Consider Special stock in MRP run

Hi all,
Is it possible to consider the special stock (table MSLB) when I run MRP (MD01)?
The type os special stock is 'O'
Thank in advance,
Felipe Simionatto
Edited by: fsimionatto on Feb 8, 2012 8:09 PM

Special stock cannot be included in the MRP run, either you have to make it unrestricted or implement a BAdI or userexit.
BAdI/Enhancement implementation may not be very reliable :
The following BAdi's are available for MRP related stuff
MD_ADD_COL_EZPS           BAdI: Extra Columns for Evaluation PP-MRP Reqmnts P
MD_ADD_COL_OVERVIEW       BAdI: Display of Additional Columns in the Material
MD_ADD_ELEMENTS
MD_ADD_ELEMENTS           BAdI for Adding Additional Requirements/Receipts
MD_CHANGE_CALENDAR        BAdI: Change Calendar for Range of Coverage Calcula
MD_CHANGE_MRP_DATA        BAdI: Change Data when Importing MDPSX
MD_DISPLAY_ELEMENT        BAdI for Changing Display of MRP Elements
MD_DISPLAY_ELEMENT
MD_EXPORT_TREE            Order Report: Export Contents of the Order Tree
MD_EXT_SUP                BAdI for Determining the Issuing Storage Location
MD_INTERACT_PLANNING      BAdI for Deactivating Changeability of MRP Elements
MD_LAST_LOT_EXACT         BAdI for Calculating Last Lot Exactly in Individual
MD_M61R_DELKZ_POPUP       Definition: Display data for MRP element (MD04)
MD_M61R_EXT_REQS_TXT      Definition: Supplement data of MRP element for ext.
MD_M61X_EXT_REQS_GET      Definition of selection of external rqmts in FuGr M
MD_MODIFY_PRODVERS        BAdI for Modifying Production Version
MD_MODIFY_SOURCE          BAdI for Modifying Source Determination in MRP
MD_MRP_LIST               BADI for further processing of MRP list
MD_MRP_PARAMETERS         BAdI: Change Planning Parameters
MD_MRP_RUN_PARALLEL       Add-Ins for parallel planning run of requirements p
MD_PIR_FLEX_CONS          BAdI for flexible planned ind. req. consumption/red
MD_PLANNING_RESULT        BADI for Issuing Planning Result
MD_PLANNING_SCENARIO      BAdI for Maintenance of Add. Parameters in Planning
MD_PLDORD_BOMEX_CIF       BAdI: Deactivation of BOM Forced Explosion in CIF
MD_PLDORD_CHANGE          BAdI for Changing Planned Orders
MD_PLDORD_POST            BAdI: Update of Planned Orders
MD_PLDORD_SCHEDULING      BAdI: Schedule Planned Orders
MD_PLDORD_TIME_STAMP      BADI for publishing time stamp problems
MD_PURREQ_CHANGE          BADI for changing purchase requisitions
MD_PURREQ_POST            BADI for updating purchase requisitions
MD_PURREQ_REL_STRAT       BAdI for Deactivating Release Strategy for MRP Purc
MD_STOCK_TRANSFER         BADI: Change the Requirement Date During Stock Tran
MD_SUBCONT_LOGIC          BADI: Determine Subcontracting Logic
Available userexits for MD01.
LMDR2001                                User exits restr. profiles of opt. pur.ord.-based load bldg
LMDZU001                                User exits in additional planning
Edited by: Jeevan Sagar on Feb 8, 2012 2:30 PM

MOPZ Issue

Dear Guru's,
After configuring the MOPZ, if we try to approve the added SP in solution manager. When I click "Confirm Files in Download Backet" under t-code solution_manager -> Change Management -> Maintenance Optimizer -> Transaction ID -> its throwing a Runtime Errors which has been mentioned below.
=====================================================================================================
Runtime Errors RAISE_EXCEPTION
Date and Time 23.12.2008 15:48:49
Short dump has not been completely stored (too big)
Short text
Exception condition "NOT_FOUND" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
Error analysis
A RAISE statement in the program "CL_SM_DATA_SENDER_RFC=========CP" raised the
exception
condition "NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
Trigger Location of Runtime Error
Program CL_SM_DATA_SENDER_RFC=========CP
Include CL_SM_DATA_SENDER_RFC=========CM003
Row 24
Module type (METHOD)
Module Name GET_DESTINATION
=====================================================================================================
OS : AIX 5.3
DB : DB2 9.5
SAP : Solution Manager 7.0
Suggestion appreciated.
regards,
Guna

Dear All,
Thanks for your suggestions...
Mr. Gagan Deep Kaus suggestion won't applicable, coz we have 3 columns in AISUSER t-code.
Mr. Paul, 1140822 has been implemented and also sub-notes mentioned also implemented.
Mr. Miguel Ariño, yes your rite we have 3 columns and I use only one customer number and also that Badi deactivated.
Still I'm facing the runtime errors and also its showing System messages in solution_manager t-code,
System Messages:
Error No destination for SAP customer number 20405164
Runtime Errors         RAISE_EXCEPTION
Date and Time          03.05.2010 20:53:36
Short text
     Exception condition "NOT_FOUND" raised.
What happened?
     The current ABAP/4 program encountered an unexpected situation.
Error analysis
     A RAISE statement in the program "CL_SM_DATA_SENDER_RFC=========CP" raised the exception condition "NOT_FOUND".
     Since the exception was not intercepted by a superior program, processing was terminated.
     Short description of exception condition:
     For detailed documentation of the exception condition, use
     Transaction SE37 (Function Library). You can take the called
     function module from the display of active calls.
Trigger Location of Runtime Error
     Program                                 CL_SM_DATA_SENDER_RFC=========CP
     Include                                 CL_SM_DATA_SENDER_RFC=========CM003
     Row                                     24
     Module type                             (METHOD)
     Module Name                             GET_DESTINATION
Could anyone suggest me a solution to close this issue.
regards,
Guna

Add Approver/ Rewiever error

Hi Gurus,
We have currently upgraded EBP 4.0 version from SP5 to SP11.
When clicking on the Add Approver button, getting pop up "No Possible Processor Found for approval task. Inform system admin" and not fetching any list of agents.
When clicking on the Add Reviewer, it is not bringing any pop up or other error/warning screen.
Please advice. Thanks in advance.
Regards,
Gopesh

Hi All,
This BADI deactivation started throwing other error message class BBP_WFL and no 038.
This problem has been resolved by changing the include LBBP_PDH_WFLF02 and function module BBP_PDH_WFL_APP_ASSIGNTYPE_GET.
Thanks everybody for your suggestions.
Regards,
Gopesh

Production Order UserExits

Hi All,
              Plz provide me with a list of PP user exits,BADI's,BTE's which trigger when a production order is released.
Thanks & Regards,
Sudheer.

Hi,
BAdis:
CEWB_CHA_MENU_EXTERN Menu Extensions in the Engineering Workbench
CEWB_COM_MENU_EXTERN Menu Extensions in the EWB (SAP Internal)
CEWB_GEN_MENU_EXTERN Menu Extensions in the Engineering Workbench
CEWB_ITM_MENU_EXTERN Menu Extensions in the Engineering Workbench
CEWB_MST_MENU_EXTERN Menu Extensions in the Engineering Workbench
CEWB_OPR_MENU_EXTERN Menu Extensions in the Engineering Workbench
CEWB_TSK_MENU_EXTERN Menu Extensions in the Engineering Workbench
CEWB_TSK_SCREENS     Screen Extensions for Task Lists in the EWB
CEWB_TSK_UPDATE      Task List Maintenance and Checks in the EWB
CRHRORG              Delete Action, Delete HR Organiz. Unit, Set Deletion Flag
CR_WORKCENTER_SELECT Performance Selection Class System for CIF PPM
EWB_SELECTION        Selection Within the Engineering Workbench
ROUTING_EXIT         User Exits for Routings
SMOD_MPRO0004        Postprocessing of forecast errors and exception messages
BADI_CY_AMT_COMPUTE BADI for KBED Amount Compute
BADI_CY_LD_DIST001   BAdI for Load Distribution During Capacity Planning
BADI_CY_SAPLCY18     Operation Status: Column Based on KBED Status
CX_OFFSET_CALID      Use of Work Center Calendar in Case of Lead/Follow-Up Time
MD_ADD_COL_EZPS      BAdI: Extra Columns for Evaluation PP-MRP Reqmnts Planning
MD_ADD_COL_OVERVIEW BAdI: Display of Additional Columns in the Material Overview
MD_ADD_ELEMENTS      BAdI for adding additional requirements/receipts
MD_CHANGE_MRP_DATA   BAdI for Changing Data When Reading In MDPSX
MD_DISPLAY_ELEMENT   BAdI for Changing Display of MRP Elements
MD_EXT_SUP           BAdI for Determining the Issuing Storage Location
MD_INTERACT_PLANNING BAdI for Deactivating Changeability of MRP Elements
MD_LAST_LOT_EXACT    BAdI for Calculating Last Lot Exactly in Individual Segment
MD_MODIFY_PRODVERS   BAdI for Modifying Production Version
MD_MODIFY_SOURCE     BAdI for Modifying Source Determination in MRP
MD_MRP_LIST          BADI for further processing of MRP list
MD_MRP_PARAMETERS    BAdI: Change Planning Parameters
MD_MRP_RUN_PARALLEL Add-Ins for parallel planning run of requirements planning
MD_PIR_FLEX_CONS     BAdI for flexible planned ind. req. consumption/reduction
MD_PLANNING_RESULT   BADI for Issuing Planning Result
MD_PLANNING_SCENARIO BAdI for maintaining addnl parameters in the plng scenario
MD_PLDORD_BOMEX_CIF BAdI: Deactivation of BOM Forced Explosion in CIF
MD_PLDORD_CHANGE     BAdI for Changing Planned Orders
MD_PLDORD_POST       BAdI for Updating Planned Orders
MD_PLDORD_SCHEDULING BAdI for scheduling planned orders
MD_PLDORD_TIME_STAMP BADI for publishing time stamp problems
MD_PURREQ_CHANGE     BADI for changing purchase requisitions
MD_PURREQ_POST       BADI for updating purchase requisitions
MD_PURREQ_REL_STRAT BAdI for Deactivating Release Strategy for MRP Purch. Reqs
MD_STOCK_TRANSFER    BADI for changing the requirement date during stock transfer
MD_SUBCONT_LOGIC     BADI for defining subcontracting logic
You can find user exits available for a particular transaction by executing the following program. Copy this code in SE38 and execute the same.
report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
         tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
   select single * from tadir where pgmid = 'R3TR'
                    and object = 'PROG'
                    and obj_name = tstc-pgmna.
   move : tadir-devclass to v_devclass.
      if sy-subrc ne 0.
         select single * from trdir where name = tstc-pgmna.
         if trdir-subc eq 'F'.
            select single * from tfdir where pname = tstc-pgmna.
            select single * from enlfdir where funcname =
            tfdir-funcname.
            select single * from tadir where pgmid = 'R3TR'
                               and object = 'FUGR'
                               and obj_name eq enlfdir-area.
            move : tadir-devclass to v_devclass.
          endif.
       endif.
       select * from tadir into table jtab
                     where pgmid = 'R3TR'
                       and object = 'SMOD'
                       and devclass = v_devclass.
        select single * from tstct where sprsl eq sy-langu and
                                         tcode eq p_tcode.
        format color col_positive intensified off.
        write:/(19) 'Transaction Code - ',
             20(20) p_tcode,
             45(50) tstct-ttext.
                    skip.
        if not jtab[] is initial.
           write:/(95) sy-uline.
           format color col_heading intensified on.
           write:/1 sy-vline,
                  2 'Exit Name',
                 21 sy-vline ,
                 22 'Description',
                 95 sy-vline.
           write:/(95) sy-uline.
           loop at jtab.
              select single * from modsapt
                     where sprsl = sy-langu and
                            name = jtab-obj_name.
                   format color col_normal intensified off.
                   write:/1 sy-vline,
                          2 jtab-obj_name hotspot on,
                         21 sy-vline ,
                         22 modsapt-modtext,
                         95 sy-vline.
           endloop.
           write:/(95) sy-uline.
           describe table jtab.
           skip.
           format color col_total intensified on.
           write:/ 'No of Exits:' , sy-tfill.
        else.
           format color col_negative intensified on.
           write:/(95) 'No User Exit exists'.
        endif.
      else.
          format color col_negative intensified on.
          write:/(95) 'Transaction Code Does Not Exist'.
      endif.
at line-selection.
   get cursor field field1.
   check field1(4) eq 'JTAB'.
   set parameter id 'MON' field sy-lisel+1(10).
   call transaction 'SMOD' and skip first   screen.
*---End of Program
Regards,
Srilatha.

ECC6 shutdown : CIF deactivation and CIF reactivation ?

Hello,
We are running SAP ECC6 EHP5 and SAP SCM 7.02/Live Cache 7.9.
I am a sap basis guy, and it is quite difficult to perform any maintenance on ECC6 which would require a shutdown ( parameter change, kernel update, memory adjustment, ...) because of the impact it has on the CIF
I just wanted to share with you our current procedure just to determine if it is indeed a common practice.
I understand that similar issues have already been discussed on sap scn threads, but most of them concern SCM/APO shutdown, like here :
How to handle CIF before we try to apply Service Packages to SCM?
I could not find any note, best practice regarding ECC6 shutdown
So, whenever we stop the ECC6 ssytem , we need to run a CIF-DEACTIVATION job, which consists of the following steps :
No. Program name/command Prog. type Parameters
1 RIMODAC2             ABAP                  DEA_ATP_CHECK
2 RIMODAC2             ABAP                  DEA_ATP_BATCH
3 RIMODAC2             ABAP                  DEA_ATP_STOCK
4 RIMODAC2             ABAP                  DEA_ATP_SALESO
5 RIMODAC2             ABAP                  DEA_ATP_PURCH
6 RIMODAC2             ABAP                  DEA_ATP_MATERI
7 RIMODAC2             ABAP                  DEA_ATP_PLANTS
This usually takes one hour.
And then after ECC6 system is restarted , we run the CIF-REACTIVATION job which consist of the following steps :
No. Program name/command Prog. type   Parameters
1 RIMODGEN             ABAP                  ATP_PLANTS
2 RIMODGEN             ABAP                  ATP_MATERIALS
3 RIMODGEN             ABAP                  ATP_PURCH_ORDS
4 RIMODGEN             ABAP                  ATP_SALESORDER
5 RIMODGEN             ABAP                  ATP_STOCK
6 RIMODGEN             ABAP                  ATP_BATCHES
7 RIMODGEN             ABAP                  ATP_CHECK
8 RIMODAC2             ABAP                  ATP_PLANTS
9 RIMODAC2             ABAP                  ATP_MATERIALS
10 RIMODAC2             ABAP                  ATP_PURCH_ORDS
11 RIMODAC2             ABAP                  ATP_SALESORDER
12 RIMODAC2             ABAP                  ATP_STOCK
13 RIMODAC2             ABAP                  ATP_BATCHES
14 RIMODAC2             ABAP                  ATP_CHECK
15 RIMODDEL             ABAP                  ATP_ALL
16 RAPOKZFX             ABAP                  ATP_GATP
17 RCIFIMAX             ABAP                  ATP_GATP
18 RDELALOG             ABAP                  ATP_GATP
This takes 7 hours !!!
I am starting to suspect that we might not be doing the "right thing", but I am definitely not an APO expert.
Could you please kindly share your practices, thoughts ?
Thanks and Regards

HI Raoul,
No need to activate and de activate CIF when ever you stop ECC system.
Reason is you will send data to APO only When ECC is not available i.e., RFCs not working then you will set up the connections and do data transfers.
Check any data transfer is happening by directly/batch. Postpone those activities..
Prior to shut down ECC/SCM send remainders to users that the systems will not be available.
Use these 2 programs from SCM side when you have stopped ECC.
RSTRFCQ1 : Stop Outbound Queue
RSTRFCQ3 : Restart Outbound Queue.
In our project we have to postpone/stop the jobs for data transfers between ECC and APO.
However you will be having daily CIF jobs to make ECC and APO in synch. So, once you re start your ECC regular CIF jobs will activate new objects(master and trnasaction data) and will deactivate lod data.
Thanks,
Bala.

BADI deactivation in ECC6.0

Similar Messages

Maybe you are looking for