Before going for Fetching Data from Memory Stack Using New Tool in Debugger. Commonly we get a necessity to add approvals for standard exchanges wherein the field esteem isn’t straightforwardly open in client exit or BADI. So assuming you are additionally battling with such prerequisite, your stand by is finished. Prapti is here to your salvage.
In this article, we will get familiar with a short and straightforward stunt to get to separate qualities standard exchange code. Fetching Data from Memory Stack Using New Tool in Debugger!
Fundamentally, we would take advantage of the Memory Stack at Run-Time involving the New Device in Debugger. Assuming that in any meeting, somebody asks you, do you realize Memory Stack Programming? Subsequent to going through this article, your response ought to be a major certain positive.
Following are the steps that need to be followed:
- Get the program name and field information from the screen (utilizing F1)
- Add a breakpoint in the exit/BADI
- Execute the exchange and actually look at the worth at runtime utilizing New Apparatus (Devices – > Exceptional Instrument – > Stacked Projects)
- Add code in the exit/BADI for getting information from the screen field
Truth can be stranger than fiction. Allow me to take an extremely straightforward ongoing reasonable model. While making a buy request in SAP, there is an arrangement to add one-time merchant subtleties. Our prerequisite is to include an Approval PINCODE length.
We were involving Really look at technique for BADI ME_PROCESS_PO_CUST for approval in PO. In any case, found that the location subtleties were not available in the BADI.
We followed the 4 stages referenced previously. We found the program name and field information.
Added the debugger and executed the exchange. In the debugger apparatus, go to New Device choice.
Alert: In the event that your debugger takes you to Standard Tab as a matter of course, you wouldn’t view as the “New Device”. Try not to overreact. Simply click Work area 1 or Work area 2 or Work area 3 and New Instrument would show up for your administration.
Go to Loaded Programs option in Special Tools.
Select Worldwide Information tab where we will actually want to see every one of the worldwide factors of each program.
Allow us now to track down the program and field for Address information.
Yeah, we got the ADDR1_DATA values. So now we reached the last step – the code :).
FIELD-SYMBOLS:<fs1> TYPE any. * Make the system know from which Program we need the data DATA:post_code(40) TYPE c VALUE '(SAPLSZA1)ADDR1_DATA-POST_CODE1'. * Assign the value to a field system ASSIGN (post_code) TO <fs1>. IF <fs1> IS ASSIGNED. * Do your validation IF strlen( <fs1> ) NE '6'. MESSAGE 'Postal Code should be of length 6.' TYPE 'E'. ENDIF. ENDIF.
Fundamentally, we just dove profound into the memory stack at the run-time and searched for all projects that were stacked in the framework for culmination of the specific exchange. Utilizing the New Apparatus, we tracked down the Worldwide Information. When you have the Worldwide Information, you can simply bring that information in your program utilizing Field Image.
Trust you like this stunt. This is a straightforward arrangement which we want to do in each task. In the event that you are a fledgling on SAP ABAP, bookmark this article. You would require this for your most memorable Memory Stack Programming.
You can execute this equivalent stunt to bring any worldwide information like table, structures, factors, objects and so on.
Note: There is a restriction. If the variable, workspace, table and so on are NOT announced as Worldwide on the stacked projects, then, at that point, we Can’t recover its worth utilizing the above strategy.
YOU MAY BE INTERESTED IN
ABAP on SAP HANA: ATC – ABAP Test Cockpit Setup & Exemption Process
WhatsApp us