Hide Button or Icon in The ABAP Report
Hide Button or Icon in The ABAP Report
Hide Button or Icon in The ABAP Report
Sometimes we need to backup or export our SAPScript code, below is the step
1. Run program RSTXSCRP througn SE38
2. Key in the FORM name, and click run button
3. Save the form with .txt extension, save the form in the desktop.
4. Now you have the SAPScript code in the txt mode
In this situation, we want to edit the payment term in of the customer under Company Data.
Basically before you are trying to use any BAPI that changing the data, run the BAPI that get the
detail from the system. As for this I'm using BAPI_CUSTOMER_GETDETAIL1.
In this BAPI you will need to enter the appropriate data to get the detail of the Customer.
Based on the data that you receive follow that and fill up in the
BAPI_CUSTOMER_CHANGEFROMDATA1.
If the return is 000, then you BAPI is execute with no error and now you can check using tcode
XD03.
Have Fun...!! :)
TRANSPORTING NO FIELDS
addition make its optimize way to make the program run faster
perhaps.
How to Add Customized Filed (KOB1) Actual Cost Line Items SAP Notes 325546
Assumption:
1. Enhancement on existing SMOD - COOMEP0
2. Using CI_RKPOS
3. Add ZZAUGBL (Clearing Document) customized field.
Steps:
1. Add the customized field in the CI_RKPOS structure.
2. Data Element should follow AUGBL field from BSEG.
6. Choose "Field Catalog Information" and in change mode, add New Entries. For this
customized field refer below figure.
Field Structure : KAEP_COAC
Field Name: ZZAUGBL
Field Group: 'K' - for customized field
7. Run back the program the customized should appear in the layout selection.
------------------------------------------------
Check table T001F and key in the program name. The Sapscript name will be at column Form
The attached report generates doxygen / plant uml documentation from an abap developoment
package.
There are the following prerequisites:
1.) you need doxygen and plantUml installed in (c:\tools\plantuml, i.e. plantuml.jar needs to be
there)
2.) you need a directory c:\src (this directory will be used as a workdirectory, files in this
directory will be created, overwritten and deleted)
4.) you need the file dp.bat in c:\tools, (you find the file in the attached as a txt file, please
rename to dp.bat)
5.) you need the report zmu_dump_class activated in your BW system. (BW 7.40).
If you run the report, you need to provide the name of a development package and then the
documentation is generated.
You find the generated documentation in c:\src\html after a successfull run of zmu_dump_class.
Please note that there is no guaranteed support its just a tool I wrote for my convenience and a
tool I think it's worth sharing.
Business Scenario: Automate freight header pricing condition type on sales order at the header
level. Currently SAP doesn't have the capability to automate header condition types. What we
mean by automate is, for example, item condition types, you can set those up with a condition
record and when certain criteria is met the record is automatically inserted into the sales order.
Transaction VK11/VK12/VK13 allows you to enter in the condition record type and then
create/change/display records for different condition types.
Solution: Put some custom code within the sales order user exit MV45AFZZ. There are several
places in which custom code can be placed in order to update the sales order header condition
type. One place the code can be put is the FORM userexit_save_document_prepare (which is the
form that gets executed one time right before the sales document gets saved. Another place and
1. Go to SE38 and enter in MV45AFZZ and click on change. (If it asks you for an object key
that means you need to create an enhancement).
2. Go down to the FORM userexit_pricing_prepare_tkomk.
3. In our instance we only wanted to update the header freight condition type on the creation of
the sales order. In order to do this you need to start your custom code with an "if" statement that
checks to make sure that t180-trtyp = 'H'. If it does, that means that it's in creation mode. The
snippet of code I'm pasting is in relation to pulling information from a custom table to determine
what the condition record should be and update the incoterms and payment terms along with the
condition record.
4. Also note in the code that there is a global variable that is set, gv_update_pricing. We had to
do this in order for the new pricing to update automatically since the terms were being updated.
This code needs to be placed in the FORM userexit_new_pricing_vbkd of user exit
MV45AFZB. I've put the code, in order to update the pricing automatically, down below also.
And again this is only done when creating the sales order.