Wednesday, November 8, 2017

Closing Cockpit Without Transport Request

Closing Cockpit without transport request:

Clocking Cockpit is used for month end/quarter end/yearend activities with some defined steps as per the client needs. There are some situations where you may have to add additional step for that month end or quarter end, in those situation we have to create that step in development system and transport that entry into production system. This process is little time consuming and client cannot wait to perform his month end/quarter end activities.

We can bypass the transport creation with standard code enhancement .Also we can put some additional conditions like based on users and system wise.

Step 1: Go to transaction code SE24 and enter object type CFC and display.

Step 2: Open the method Transport and click on Enhance button.

Step 3: Now click on show implicit or explicit enhancements options.

Step 4: Create enhancement on the top of the code and add the logic to skip the code inside the method when user accessing closing cockpit transaction.

Test Data creation at Runtime from SRM to ECC

Capture test data at runtime in standard function modules from SRM to ECC.

In day to day life, we come across situations where we have to debug standard code or transaction codes for different issues from SRM to ECC systems. Being standard code, sometimes it may take days to find exact root cause of the issue. Finally after completing the analysis we may end up saying as data issue, based on the data provided at the time of updating or posting to standard FM’s BAPI_PO_CHANGE or BAPI_PO_CREATE etc... So, it will be useful if we have test data created in those function modules at the time of transaction executed.

Below are the steps to activate test data creation:

Step 1: On ECC, set the parameter FBGENDAT ‘X’ in the backend system for the RFC user of the SRM system.

Step 2: on ECC, execute report FBGENDAT in the mode ‘B’.

Step 3: on SRM, reproduce the issue from start.

Step 4: on ECC, check if a test data record was generated in the function builder.

Step 5: on ECC, deactivate the generation of test data records by deleting the entries in report FBGENDAT and resetting the user parameter.