SAP ABAP Tutorials

SAP ABAP Interface Detailed Design

2009-01-21T05:01:00.000-08:00

Interface Detailed Design

TABLE OF CONTENTS

1. INTRODUCTION 3
1.1. Purpose of this Document 3
1.2. EDI System Configuration 3
2. INTERFACE DESIGN GUIDE 4
2.1. Interface Configuration 4
2.2. Outbound Batch Processing 4
2.3. Inbound Batch Processing 5
2.4. Interface Housekeeping 5
2.5. Potential Errors and Recovery 6
2.6. Archiving and Backup 6

1. INTRODUCTION
1.1. Purpose of this Document
The purpose of this document is to outline the technical design of the EDI interface from SAP to the EDI subsystem. The high-level details of the proposed solution may be found in the EDI Scope document, as well as the EDI Functional Specification document. Further information on the interface may be obtained by reading the EDI Production Setup Guide.
1.2. EDI System Configuration
The EDI system configuration will initially consist of a SAP client reading in and writing out IDoc format files to a UNIX directory. This will occur at a time defined by the interchange agreements set up by the business.
2. INTERFACE DESIGN GUIDE

The diagram above gives a diagrammatic representation of the EDI process, including the interfacing with the subsystem. A technical overview of the process is described in the following sections.
2.1. Interface Configuration
The details of the interface configuration is described in the documents “EDI Production Setup Guide” and “NFS Setup Guide”.
2.2. Outbound Batch Processing
A SAP outbound batch job will need to be scheduled to run on a daily basis at a fixed time. This job will need to be run before a corresponding inbound job executes on the EDI subsystem translation software, allowing sufficient time to allow the outbound job to be completed

The transaction that needs to be run is transaction WE14, running program RSEOUT00 with a variant, specifying the receiver port (such as SAPF01) and the message type (ORDERS, ORDCHG).
Since a fixed outbound IDoc filename (as opposed to dynamic naming using a SAP function) will be used for processing, it is not essential that the file be deleted after being read in by the subsystem. This file will be overwritten when the next run of the outbound batch job occurs.

Note that the EDI system administrator will be able to check on the date and time of a particular file, either by examining the SAP log (using transaction WE05), or alternatively, examining the date and time stamp of the file at the Unix level using the Unix ‘ls -l’ command in the EDI subdirectory (/home/edi). This outbound IDoc file may be copied at the Unix system level for diagnostic or archiving purposes.

The main routine monitoring activity for outbound jobs requires that the shared EDI directory is examined after every scheduled batch job to ensure that the batch job has run, and that a file with a date stamp that corresponds to the time of the batch job exists.

Transaction BD88 is useful for resubmitting IDocs which have not been correctly processed. Note that IDocs can be manually edited if required, using transaction WE02 or WE05.
2.3. Inbound Batch Processing
A SAP Inbound processing job will need to be run on a daily basis at a fixed time. Ideally, inbound and outbound processing should not be scheduled at the same time to prevent any confusion, though this is possible should it be required. This process should only be run after the corresponding EDI subsystem processing has been completed. Transaction BD87 can be used to read in IDocs if required. IDocs can be manually edited if required, using transaction WE05, or transaction WE19.

2.4. Interface Housekeeping
Interface housekeeping is minimal, since all files handled at the interface level are overwritten or deleted after each exchange. Therefore, no maintenance is required at the interface level.

2.5. Potential Errors and Recovery
Due to limitations of the Gentran Director software being used, the integration of SAP and the EDI subsystem is very limited. No status information is communicated from the subsystem to SAP or vice-versa. Therefore regular monitoring after each batch job (and before each subsequent batch job in the same direction of transfer) is required to ensure that no files are overwritten.

If jobs have not been successfully executed, a manual job should be scheduled immediately. If files are accidentally overwritten, all EDI messages that were transferred in a particular direction will have to be rewritten by the originating system (SAP or Gentran).
2.6. Archiving and Backup
There will be no archiving or backup of data files at the interface level, but strategies for this will have to be in place for SAP and Gentran.

SAP ABAP User Exit Overview

2009-01-21T04:52:00.001-08:00

What is a User Exit?

You can use User Exits to adapt the SAP System to your company's specific requirements. They do not involve modifications to the original coding; instead, they consist of a separate area that is defined by SAP and shipped with the standard system either empty or with default values. You can individually configure and activate these system extensions. By enhancing the SAP software via user exits, we avoid modifications in the traditional sense.

A further advantage of user exits is that programs developed with user exits remain unchanged during upgrades to the SAP software.

User exits are not affected by SSCR, because the customer-specific parts of the user exits are implemented in the customer name range.

Categories of User Exits

Three types of user exits exist:

Function exits. Function exits are function modules that have been defined by SAP and that you can activate. The application developers determine which data is passed on and define the function groups and function modules in the function library (with short text and interface, but without coding).
Menu exits. Menu exits can be used to activate menu items and furnish them with additional functionality.
Screen exits. Screen exits enable you to add additional fields to a screen.

Request for Expansion of User Exits

If you would like to have additional functionality at certain places in the R/3 System, enter a problem message in OSS in which you name the specific application. SAP will process your request and decide whether the functionality can be implemented in the next upgrade or wheth er a user exit can be provided.

Overview of User Exits

You can display a list of existing enhancements in the system through the following menu path:
ABAP/4 Workbench B Environment B Enhancements B Project administration B Utilities B SAP enhancements.

http://sapr3.tripod.com/sapab013.htm

SAP User Exits Routine

User exits are routine which SAP allows you to add in additional customized programs process without affecting the standard SAP programs.

form userexit_xxxxx
........................
endform

In VL01 - Create Delivery Order, standard program SAPMV50A, the standard program did not check for storage location equal to space, and delivery quantity less than one when the user click the save button. Therefore I have to insert the additional checking into the userexit routine.

Steps:-

Goto transaction VL01 to pick a Sales Order for delivery (you don't have to save the data)
In the initial screen, click System -> Status -> Double click on Program (Screen)
In the dialog program SAPMV50A, click Edit -> Search/replace
Type userexit in the Find field, then click the In program radio button and hit Enter
A number of userexit routine will be display. You'll have to roughly decide which is the correct userexit routine to used.

form userexit_save_document_prepare.
case xlips-pstyv.
when 'TAX' or 'REX'.
* Accept this two Delivery item category

when 'REN'.
if xlips-lgort = space.
* Reject this Delivery item category
message e001.
endif.

when others.
if xlips-matnr <> space.
* Check storage location not space
if xlips-lgort = space.
message e002.
endif.
* Check delivery quantity not zero
if xlips-pikmg < 1. message e003. endif. endif. endcase. endform.

SAP Transaction Codes

2009-01-21T04:37:00.000-08:00

SAP Transaction Codes

SPRO DEFINE ITEM CATEGORY

MM01 CREATE MATERIAL

MM02 MODIFY MATERIAL

MM03 DISPLAY MATERIAL

MMS1 CREATE MATERIAL MASTER

MMS2 CHANGE MATERIAL MASTER

MMS3 DISPLAY MATERIAL MASTER

MB1C MAINTAIN STOCK

MMPI INITIALISE PERIOD FOR MASTER MATERIAL RECORDFROM CO CODE

MMBE CREATE STOCK

MM60 MATERIAL LIST

XD01 CREATE CUSTOMER

XD02 MODIFY CUSTOMER

XD03 DISPLAY CUSTOMER

VA01 CREATE ORDER

VA02 CHANGE ORDER

VA03 DISPLAY ORDER

VA11 CREATE INQUIRY

VA12 CHANGE INQUIRY

VA13 DISPLAY INQUIRY

VA21 CREATE QUOTATION

VA22 CHANGE QUOTATION

VA23 DISPLAY QUOTATION

VD02 CHANGE SALES PROSPECT

VD03 DISPLAY SALES PROSPECT

VD04 DISPLAY CHANGES

VD06 FLAG FOR DELETION

VK11 MAINTAINING PRICING

VK0A ASSIGN G/L ACCOUNT GENERAL

VOK0 PRICING

VOR1 DEF COMMON DIST CHANEL

VOR2 DEF COMMON DIV

VOV6 DEFINE SCHEDULE LINES

VOV8 DEFINE SALES DOC TYPE

VOFA CREATE/OR CHANGE BILLING TYPES CONFIGURATION

V129 DEFINE INCOMPLETENESS SCHEMAS FOR FOREIGN TRADE

V149 ASSIGN INCOMPLETENESS SCHEMAS FOR COUNTRY CODE

CA01 CREATE ROUTING

CA02 EDIT ROUTING

CA03 DISPLAY ROUTING

CS01 CREATE BOM

CS02 CHANGE BOM

CS03 DISPLAY BOM

OVK1 DEFINE TAX DET RULES

OVK3 DEF TAX REL OF MASTER RECORDS CUSTOMER TAXES

OVK4 DEF TAX REL OF MASTER RECORDS MATERIAL TAXES

OVR6 DEF LEGAL STATUSES

OVS9 DEF CUSTOMER GRP

OVRA MAINT STATISTICS GRPS FOR CUSTOMERS

OVRF MAINT STATISTICS GRPS FOR MATERIAL

OVXC ASSIGN SHIIPING POINT TO PLANT

OVX6 ASSIGN PLANT TO S.O AND DIST CHANEL

OVLK DEFINE DELIVERY TYPE

OVSG DEFINE INCOTERMS

OVLH DEFINE ROUTES

OVXM ASSIGN SALES OFF TO SALES AREA

OVXJ ASSIGN SALES GRP TO SALES OFFICE

OMS2 MATERAIL UPDATE

OVLP DEFINE ITEM CATEGORY FOR DELIVERY

OX10 ASSIGN DEL PLANTS FOR TAX DET

O/S2 DEFINE SERIAL NO PROFILE

O/S1 DEFINE CENTRAL CONTROL PARAMETERS FOR SR NO

OBB8 DEFINE TERMS OF PAYMENT

OKKP ACTIVATION OF COMPONENETS

VB01 CREATE REBATE AGGREMENTS

VB02 CHANGE REBATE AGREMENT

VB03 DISPLAY REBATE AGGREMENT

VB31 CREATE PROMOTION

VB32 CHANGE PROMOTION

VB33 DISPLAY PROMOTION

VB21 CREATE SALES DEAL

VB22 CHANGE SALES DEAL

VB23 DISPLAY SALES DEAL

VB25 LIST OF SALES DEAL

VB35 PROMOTION LIST

VKA4 CREATE ARCHIVE ADMINISTRATION

VKA5 DEL ARCHIVE ADMINISTRATION

VKA6 RELOAD ARCHIVE ADMINISTRATION

VC/1 CUSTOMER LIST

VC/2 CREATE SALES SUMMARY

VDH2 DISPLAY CUSTOMER HIERARCHY

VF01 CREATE PROFORMA INVOICE

VF02 CHANGE PROFORMAINVOICE

VF03 DISPLAYPROFORMA INVOICE

VF07 DISPLAY FROM ARCHIVE

VF11 CANCEL BILL

VFX3 BLOCKED BILLING DOC

VFRB RETRO BILLING

VF04 MAINTAIN BILL DUE LIST

VF06 BACKGROUND PROCESSING

VF21 CREATE INVOICE LIST

VF22 CHANGE INVOICE LIST

VF23 DISPLAY INVOICE LIST

VF44 MAINT REVENUE LIST

VF45 REVENUE REPORTS

VF46 MAINT CANCELLATION LIST

VF31 ISSUE BILLING DOC

VFP1 SET BILLING DATE

VARR ARCHIVE DOCUMENTS

VL01N CREATE DELIVERY

VL02N TO CHANGE DELIVERY WHICH IS ALREADY CREATED

VL03N DISPLAY DELIVERY

V/08 TO CHANGE CONDITION (PR PROCEDURE)

V/30 DEFINE PRINT PARAMETERS

FD32 SETTING CREDIT LIMIT FOR CUSTOMER

/NSM12 TO REMOVE LOCK ENTRY

SM30

ND59 LIST CUSTOMER MATERIAL INFO

VB0F UPDATE BILL DOC

SAP Transaction Codes
More SAP ABAP Tutorials

Tokenization as a means of securing credit card numbers

2009-01-12T10:23:00.001-08:00

My previous blog post titled Securing credit card account numbers in SAP focused on implementing functionality provided by SAP for encrypting credit card numbers stored in the SAP ERP database. In an update I also included a brief reference to encryption functionality in the SAP CRM database. FAQ OSS notes mentioned in the post provide the necessary information to implement the SAP standard encryption functionality and thus secure the payment card and credit card numbers stored in your SAP applications.

At the end of the post I mentioned several items that you should be aware of when implementing the standard SAP functionality which may prevent compliance with PCI DSS requirements. I then alluded to Tokenization as a means of addressing the additional items. In this post I want to explore the differences between SAP's standard encryption offerings in each application and tokenization as an application independent encryption approach.

Many applications provide encryption functionality which is specific to that particular product. SAP's encryption offering for credit card numbers in the SAP ERP and CRM applications is one such example. The encryption functionality is designed to work only with that application - specifically by encrypting the credit card number data stored in the database. Should data need to be passed between applications, such as order data being replicated from the SAP ERP to SAP CRM system, the data must be decrypted in the source application passed in an unencrypted form (and therefore potentially logged in an unencrypted format) and finally encrypted in the target application. Using this application specific encryption approach has the following weaknesses:

Encryption solutions on each application must be setup, maintained and managed

Encryption keys in each solution must be managed independent of other solutions

Encryption keys must be rotated independently of other solutions

Increased number of encryption solutions require additional IT staff time for management and maintenance

Disparate encryption solutions increase security risks if maintenance is not always kept current

Encrypted data must first be decrypted before being passed to other applications and then re-encrypted before being stored by the target application

A typical enterprise with an SAP system, a web store and a payment application each storing encrypted credit card data locally using application specific encryption applications would have an architecture which look like this:

Implementing a solution which Centralizes and Tokenizes the credit card number data in a secure data vault would change the architecture to look like the following:

This solution would extract the unencrypted card numbers from the various applications, consolidate the application specific encryption functionality into a single, central solution and would simplify key management and key rotation functions. Centralization and Tokenization would specifically help address the following PCI DSS requirements:

Additional advantages to this approach would include the following:

One centralized storage location of all encrypted credit card number data

All applications would store tokens at the database level rather than unencrypted or encrypted card numbers - Security At Rest

All application interfaces could pass tokens rather than encrypted or unencrypted card numbers - Security In Transport

Rotation of encryption keys would be performed centrally and would be transparent to other applications as the tokens would remain unaffected

Centralized logs can be kept of all decryption attempts from all source systems thereby providing a valuable audit trail

If an external, third-party solution is used the risk of data loss in a breach of internal systems is greatly diminished - only tokens would compromised, not the encrypted data or encrypted keys

Finally, let's take a look at how the workflow of processing of a credit card authorization would look in an enterprise using SAP along with a Centralization and Tokenization solution:

As enumerated above, there are clearly many advantages and benefits to using a token-based solution for securing credit card details not only in SAP by across the enterprise. The token-based approach is currently not supported by standard SAP functionality, but is supported by solutions from third-parties like Paymetric.

As scrutiny increases surrounding how companies are securing sensitive customer data, such as credit card numbers, serious consideration should be made of token-based solutions. Merchants who choose to outsource the storage of this sensitive data have less risk of embarrassing data loss in the event of a system breach as only tokens would be stored locally. All encrypted data and keys would be stored by the external solution this greatly diminishing a Merchant's exposure and potential public relations nightmare.

Free SAP Interview Questions

SAP MDM Tutorials

SAP MDM Interview Questions

SAP Netweaver Tutorials

Creation of Transparent Table 3

2009-01-09T04:02:00.001-08:00

Creation of Transparent Table 3

Now it asks for Domain creation. Press Yes.

Give short description in short text field. Enter the data type and no. characters, Press Enter.

Then Press on Activate button or Press Ctrl+F3.

Save this as a local object.

Press enter.

Now you will get the following screen. Press Back button.

Activate the data element By pressing Activate button or Pressing Ctrl+F3.

Press enter.

Press Back button.

Now we created two fields. And Data elements and Domain for these two fields.

Now we have to maintain the technical settings. Press on Technical settings button.

Give the data class and size category of the table as per the requirement.

And press the back button.

Now activate the table by pressing the activate button or CTRL+F3.

Press enter.

Now you will get the following screen.

Now enter the data into table. Go to Utilitiesà Table contents à Create Entries.

Now enter the data in the fields and Save it.

You will get the following screen after clicking the Reset Button.

Enter the data for the second entry into the table.

Save it and press reset.

You will get the following screen.

44. Again enter the data for the third entry.

45. Press save, Reset (Optional) and Back button.

46. Now you will get the following screen.

To see the table contents go to Utilities à Table contents à Display. Or press Ctrl+Shift+F10.

You will get the following screen.

Press on run button or press F8. Now it will display the table contents.

Now enjoy by creating tables on your own.

Creation of Transparent Table 1

2009-01-09T03:49:00.001-08:00

Creation of Transparent Table 1

Now it will ask for domain creation. Press Yes.

Give short description for that domain which you are creating. And mention the data type in data type field and length in no. characters field an press ENTER.

Then press Ctrl+F3. It will ask for save before activation. Save it as a local Object.

Press Enter.

Then the following screen appears. Press on back button.

Press Ctrl+F3. You will get the following screen. Press Back button.

You will get the following screen.

Create one more field ZNUM and give data element name as ZNUM_DE. And double click on ‘ZNUM_DE’

Save it by pressing Yes.

Now it will ask for the data element creation. Press Yes.

Give short description of the data element. And give the lengths and field labels accordingly in Field label tab.

Press on Definition tab and give the domain name in Domain field. Double click on ZNUM_D.

It will ask for save. Press Yes.

Save it as a local Object.

Creation of Transparent Table

2009-01-09T00:57:00.001-08:00

Creation of Transparent Table

Enter the table name and press Create

Enter the description, Delivery class and check on table maintenance allowed. Then click on the tab Fields.

Enter the ZCHAR in fields tab and ZCHAR_DE in field type tab.

Double click on ZCHAR_DE. Then it will ask for Save. Press ‘YES”.

Save it as a local object on pressing Local object button

Now it will ask for the creation of the data element. Press Yes.

Click on the Field label tab and enter the lengths and descriptions accordingly.

Then press Definition tab and enter the domain.

Double click on that zchar_d to create domain, then it will ask for save before going next screen.

Press Yes.

Save it as a local object.

SAP ABAP Tutorials

SAP ABAP Interview Questions

SAP ABAP Tutorials

2009-01-09T00:51:00.001-08:00

Dictionary

* Creating a Transparent Table (More details)
* Creating a structure in ABAP Dictionary (More details)
* Creating Search helps (Elementary and collective) (More details)
* Creating a secondary index (More details)
* Working with table maintenance generator (More details)
* Creation of a Logical Database (More details) NEW

SAP ABAP Tutorials.

Direct document objects

2009-01-09T00:05:00.000-08:00

Direct document objects

Dynamic documents allow you to create HTML like document screens.  Click here for examples.
Demonstration SAP programs which use direct document objects all start with 'DD_'. So you could
either perform a value help on 'dd_*' or look below for example dynamic document programs.

*DD Programs

DD_ADD_FORM_BUTTON    Buttons on Forms of Dynamic Documents
DD_ADD_FORM_INPUT               Interactive Elements: Forms with Buttons
DD_ADD_LINK                     Interactive Elements: Links
DD_ADD_LINK_SCROLLED           Interactive Elements: Links
DD_ADD_PICTURE                  Display of SAP icons and pictures stored
   in the BDS
DD_ADD_TABLE                    Tables in Dynamic Documents
DD_ADD_TEXT                     Text output in dynamic documents
DD_ALV_FREE_TOP                 ALV use with definable page header
DD_ALV_STANDARD_TOP             ALV use with standard page header
   (REUSE_ALV_COMMENTARY_WRITE)
DD_CORRECT_TYPD_TRDIR           DDIC: Correct SUBC Entries for Type Groups
DD_F4_START_INDX                Starts indexing to synchronize an
   external index
DD_KEN_HELP_TYPES_GENERAL       Show help objects from Info Repository
DD_KH_KONTEXT                   Display online docu (HTML Browser) for a
   context
DD_SIMPLE_ALV_TOP               Demo Program Change of ALV TOP with
   Dynamic Documents
DD_SPLIT_DOCUMENT               Distribution of areas on dynamic documents
DD_START                        Program DD_START
DD_STYLE_TABLE                  Style types and list colours for dynamic
   documents, print

SAP dynamic document example screens

Below is a couple of screen shots of SAP dynamic documents, so you can get a feel of what they look like and whether they would be of any use to you!

Direct document objects

SAP ALV Reports

2009-01-09T00:02:00.000-08:00

SAP ALV Reports

	ALV tree using Objects
	ALV using Grid Function Modules
	ALV using List Function modules
	ALV using GRID Objects(Methods) on a screen

SAP ALV Reports

ABAP Reporting - Example code and information on various areas of ABAP reporting

2009-01-08T23:57:00.000-08:00

ABAP Reporting - Example code and information on various areas of ABAP reporting

[+] Advanced List Viewer(ALV)
Example code and information on ALV reporting

[+] Dynamic document objects
Example code and information on creating dynamic document objects

[+] Selection screen Setup/Processing
Examples of various selection screen development techniques

[+] Progress Indicator (Also Stops report timeout)
Implementing a progress indicator

Send SAP mail to users workplace inbox (SBWP)
Sending internal emails with SAP

Automatic refresh report
Creating reports that automatically refresh themselves

ABAP Reporting - Example code and information on various areas of ABAP reporting

Processing Keys In TC MD02

2008-12-29T03:01:00.000-08:00

Explain about processing keys in tc md02 ie netch, netpl etc.

By : Jia

Processing Key :MD02

1. Regenerative planning (NEUPL) : System plans all the materials that are contained in the planning file

2. Net change planning (NETCH) or Net change planning in the planning horizon (NETPL) :The system only plans materials that have undergone a change relevant to MRP since the last planning run .

NETCH: In net change planning only those materials are planned for which the net change planning indicator in the planning file has been set as a planning file entry. The system usually sets the indicator automatically as soon as a change is made to the material that is relevant to MRP.

NETPL:The system only plans materials that have undergone a change that is relevant to the planning run within the period which you defined as the planning horizon. The system sets the net change planning horizon indicator automatically for these materials

Remember the following point : The changes cause an entry in the planning file to be made:

Changes to stock, if these change the stock/requirements situation of the material
Creation of purchase requisitions, purchase orders, planned orders, sales requirements, forecast requirements, dependent requirements or reservations
Changing to fields that are relevant to the planning run for these receipts and issues or in the material master
Deleting receipt or issue quantities

Total Planning & Netch, Netpl, Neupl

2008-12-29T02:56:00.000-08:00

What is the difference in between total planning & netch, neupl, netpl?

1. Regenerative planning (NEUPL): System plans all the materials that are contained in the planning file

2. Net change planning (NETCH) or Net change planning in the planning horizon (NETPL): The system only plans materials that have undergone a change relevant to MRP since the last planning run.

NETCH: In net change planning only those materials are planned for which the net change planning indicator in the planning file has been set as a planning file entry. The system usually sets the indicator automatically as soon as a change is made to the material that is relevant to MRP.

NETPL: The system only plans materials that have undergone a change that is relevant to the planning run within the period which you defined as the planning horizon. The system sets the net change planning horizon indicator automatically for these materials

Remember the following point : The changes cause an entry in the planning file to be made:

Changes to stock, if these change the stock/requirements situation of the material
Creation of purchase requisitions, purchase orders, planned orders, sales requirements, forecast requirements, dependent requirements or reservations
Changing to fields that are relevant to the planning run for these receipts and issues or in the material master
Deleting receipt or issue quantities

Why Planning file entry still Exists?

2008-12-29T02:54:00.000-08:00

Does anyone know why a planning file entry would exist for NETCH or NETPL when there has been NO activity on the material since the last planning run? No movements, no PO's created, no Orders taken, no activity whatsoever . . . and MRP ran, created a planned order, which was converted to a requisition and then a PO. This PO was converted for a date earlier than what MRP recommended.

Now each time MRP runs, we get exception #15 - delay the order until later (gives date). We don't change it and the planning file entry doesn't go away, even after the run.

Found a note that seemed to apply, but . . . I guess it doesn't really.

"If the planning run terminates for a material with planning file entry on account of an error message, the planning file entry is not deleted if this is not explicitly set in customizing. In transaction OMDY, you can set for which errors (message number) you want the planning file entry being deleted."

I thought this was my answer. However, after looking in OMDY - the message #015 = Dates incorrect (start date > finish date). And message #15 = Enter value for version number increment (VersNumIncr.).

Neither of these defines my MRP List exception message 15 = "Postpone process (28.06.2004/26.06.2004)" - on a current date of 03/06/2004. It's CLOSE, but not the first message.

So if I set the field for the deletion of the planning file entry, it still wouldn't affect my real problem - trying to get this entry to 'go away' after doing what it was supposed to do.

Please Check CS15 - where used list. May be this material has been added to a BOM of a product/Assy, which has caused an entry in planning file.

Check MD04 for the source of reqt.

Also check MD63, if a PIR exists.

If not, delete from planning file. Try report RMMDVM10 - consistency check

PP - The Common Planning Strategy used

2008-12-29T02:52:00.000-08:00

The planning strategies are maintained in Customizing for Demand Management in SM30 - V_T461S.

Define the Planned Requirement Type and assign the requirement class in OMP1.

Define the requirement class in OMPO.

Check the independent requirement and consumption of requirement class in OMPC.

Maintain the message for invalid requirement type in OMPJ.

You define the strategy group in SM30 - V_T461P.

You define the Plant to MRP group in SM30 - V_T438M_S.

Maintain the consumption mode and period of adjustment in SM30 - V_T438M_V.

Listed here are some common used planning strategies :-

Strategy 10 in summary :-

1. Sales Order creation - no impact.

2. Goods Receipt - reduce the planned independent requirement during MRP run
For e.g. if PIR is 100, quantity remained as 100 in PIR, however during MRP run,
100 will not be included in the MRP planned as stock is available.

3. Delivery - minus the quantity for the oldest planned independent in demand management.
For e.g. if PIR is 100 and delivery 90, PIR becomes 10 (withdrawal 90).

10 LSF Make-to-stock production KSL Sale from stock without independent
requirement reduction

Choose this strategy if you want production to be determined by a production plan (Demand Management) and if you do not want sales orders to influence production directly.

You must maintain the following master data for the finished product:

Strategy group 10 on the MRP screen.
Item category group (for example, NORM) on the Sales Organization screen.
Availability check field in Customizing so that you perform an availability check
without replenishment lead times (in the standard system, you must enter 02 here).

In net requirements planning according to strategy 10, the order does not create a requirement; the sales order is displayed, but does not generate planned orders.

The planned independent requirement is reduced during processing of the goods issue.
Old quantities can still be retrieved by using either
Goto -> Schedule line history in Demand Management, or by using the total requirements list
(Evaluations -> Display total requirements from the Demand Management menu).
The quantities issued are displayed in the Withdrawal quantity field.

The system always reduces the oldest planned independent requirements unless the consumption fields (Consumption mode, Fwd consumption per., Bwd consumption per.) are maintained in the material master or in the MRP group.

11 BSF Gross planned independent requirements KSL Sale from stock without independent
requirement reduction

Strategy 11 in summary :-

1. Sales Order creation - no impact.

2. Goods Receipt - minus the quantity for the oldest planned independent in demand management.
For e.g. if PIR is 100 and delivery 90, PIR becomes 10 (withdrawal 90).

3. Delivery - no impact as delivery is issue from sales order.

This strategy is particularly useful if you need to produce, regardless of whether you have stock or not. For instance, steel or cement producers might want to use this strategy because they cannot shut down production; a blast furnace or a cement factory must continue to produce, even if this means having to produce to stock.

You need to maintain the following master data for the finished product:

Maintain strategy group 11 on the MRP screen.
Set the Mixed MRP indicator to 2 on the MRP screen.
Maintain the item category group (for example, NORM) on the Sales Organization screen.
Maintain the Availability check field so that you perform an availability check without the replenishment lead time (checking group 02 in the standard system).

Strategy 10 11

Stock is taken into account Yes No

Reduction of planned independent
requirements takes place during … … goods issue for ... goods receipt for a production
the delivery order (discrete production),
for a planned order (repetitive
manufacturing), or for a purchase
order (trading goods).20 KE Individual sales order without
consumption

Strategy 20 in summary :-

1. Sales Order creation is the only impact.

2. Demand management not in used.

In make-to-order production, a product is produced specifically for an individual sales order. This planning strategy is used when planning of the (parent) product is not required or not possible. Neither Demand Management is involved in this process, nor is there an allocation mechanism. Orders are taken as they come. This strategy represents a production procedure in which each product is only produced once, although over time the same or similar production processes are repeated. Each product is specifically produced for an individual customer so that the finished product is rarely placed in stock.

You also must maintain the following master data settings for the finished product:

Strategy group 20 on the MRP screen
Item category group (such as NORM) on the Sales Organization screen

Sales Order -> MRP -> Customer Stock Finished Product -> Delivery ----+
^ |
| |
+-------------------------------------------------------------------------+
Reduction

40 VSF Planning with final assembly KSV Sales order with consumption

Strategy 40 in summary :-

1. Stocks on hand reduces the PIR during MRP run.
e.g. if stock is 100 and PIR is 100, MRP run will not prompt 100 for procurement.
if stock is 0 and PIR is 100, MRP run will prompt 100 for procurement.

2. Sales order creation reduces the PIR.
e.g. if PIR is 100, sales order 90, PIR becomes 10 (withdrawal 90).

3. Delivery reduces the Sales Order.

This strategy is probably the most widely used make-to-stock strategy. It makes sense to use this planning strategy if you can forecast production quantities for the final product.

Planned independent requirements are consumed by incoming sales orders so that the master plan is always adjusted to suit the current requirements situation. This means that the important feature of this planning strategy is that you can react quickly to customers’ requirements. The smoothing of the master plan is less important.

You must maintain the following master data for the finished product in the material master:

Strategy group 40 on the MRP screen.
Consumption parameters (Consumption mode, Bwd consumption, Fwd consumption) to allow
consumption of independent requirements. If no consumption parameters are maintained in the
material master, the system uses default values are taken from the MRP group.
To control consumption, you maintain a consumption mode as well as a consumption period.

Item category group (for example, NORM) on the Sales Organization Data screen.

Four important points :-

1. Planned independent requirements are used to trigger the procurement and production of
the necessary assemblies and components before receipt of the sales orders.

2. As soon as the sales order is received, it consumes the planned independent requirements.

3. An ATP (available to promise) logic during sales order processing will checks whether
sufficient planned independent requirements have been planned to cover the sales order.

4. Requirements from the sales orders are passed on to production and can lead to changes
made to procurement if the requirements from the sales orders exceed the planned
independent requirement quantities. If there is insufficient coverage of components
(the sales order quantities exceed the planned independent requirement quantities), the
sales orders cannot be confirmed. The system therefore automatically adjusts the master
plan. Planned independent requirement quantities that are left unconsumed increase the
warehouse stock of the finished product.

Questions on MRP Group and MRP Controller

2008-12-29T02:51:00.000-08:00

MRP groups are used when the plant division for planning is not enough for the division of the different materials MRP requirements. You assign different groups according to the requirements to run MRP (different Settings). These settings will be taken in account when you run MRP for single item or total planning.

MRP controller is the person in charge of the MRP run for the materials. It is still a further division on your MRP. This is work load related. You can have one MRP controller for materials with different MRP groups.

On your MRP group, you will define the parameters for the MRP run. These parameters are calculated in accordance with the settings on your material master MRP views.

Available stock =
Plant stock - safety stock +
receipts of (purchasing orders + purchasing agreements + production orders) - required quantity.

This means that all the requirements are calculated in the bases of your material master settings and your MRP group settings.

What if nothing happens when you run MRP?

The reasons could be :-

- You have purchase requisitions that are delayed but the delivery time has not been updated on the system.

- The settings on your material MRP screens are not correct, i.e. your material have not yet
entered the re-order point level.

- Your requirements have not been taken in account when running MRP.

Assuming that everything is well and the requirement has been calculated, go to transaction code MD04 and verify that the different requirements are reflected in the MRP list and also if there is any purchase requisition scheduled by the system. Verify also if there is any other delivery schedule that will exceed the actual requirements.

If the purchasing requisition is there, the only thing that you have to troubleshoot is the message to tell you that the purchasing requirement was calculated.

If the requirement is not there, re-visit your material master and check your settings for the MRP group.

What is the real meaning and usage of the followings configured in PP:
1. MRP Controller;
2. Schedule margin key;
3. MRP group;
4. MRP profile.

1. MRP Controller;
This will help you to group the material for some controlling purpose. You can run mrp by mrp controller.
you can do evaluation by mrp controller. This will help us if have different people in one organisation involved in purchasing.

2. Schedule margin key;

This will help you to determine the floats. In case if you have production order you can see the impact of floats

3. MRP group;

This will help you for the material to reac in tems of the settings made relavant to each group. To know more details on the group you can chek the tcode oppr.

4. MRP profile
We can have some prefixed datas in the profile and and we can enter teh profile for diff material so the values will copied as defaulted in the profile.

Define Safety Stock Availability

2008-12-29T02:50:00.002-08:00

The IMG can be set in SM30 - V_438M_S

You define per plant and per MRP group the percentage of the safety stock that is to be available for planning. This helps to avoid a situation where order proposals are created unnecessarily by the system to cover small shortage quantities.

For example:

Mat. 1 Mat. 2 Mat. 3

Safety stock: 100 pc 100 pc 100 pc

available for planning: 0% 50% 50%

Shortage quantity 1 pc 1 pc 51 pc

Order proposal quantity
for lot-for-lot order qty 1 pc 0 pc 51 pc

Purchasing processing Time - OPPQ

2008-12-29T02:50:00.001-08:00

Please refer above subject and would like to do following. External Processing Time I have set in using OPPQ. My client want this time set differently for different Vendor. Is there any userexit or customization settings?

For MRP to take lead time by supplier, you need to have 3 settings:

1) The config in OPPQ - External procurement at plant level (or OPPR at MRP grp - Scheduling/doc. type) should have the check box marked to read SchedAgreem/Inforecord leadtime (T399D-GTERM)

2) You should have a contract/schedule agreement, or a purchase info record maintained for that plant-material-vendor combination

3) You should maintain source list (ME01) for the contract/schedule agreement, or info record. This changes the default behavior of MRP to use leadtime by supplier, rather than material master leadtime. When both contract and info record exist, the contract will take precedence.

Please watchout for the case if you're already using contracts/info records in procurement, but not using them for planning. In this case your leadtime data in these documents may be incorrect, or may be left blank - this will be interpreted as zero if you make this change implementation, as mentioned in the steps above.

Calculation to determine the delivery date and release date

2008-12-29T02:49:00.000-08:00

There have been three parameters that SAP will take it into calculation to determine the delivery date and release date during material requirement planning. They are -

1) Planned Delivery Time which is the vendor-dependent lead time being measured from the time PO is outputted (for sending to the vendor) till the time the shipment is delivered at the warehouse.

2) GR processing time represents the necessary period of time being required for receipting the shipment into the warehouse. This period is, usually, for quality and quantity inspection.

3) Purchasing Processing Time. This is the internal required time for processing the purchasing document (Purchase Requisition) till Purchase Order. You can set it up plant-wise via Transaction OMI8.

With these three parameters, it is possible that you can set it up correctly in your system to enable the appropriate planning of your material requirement.

GR processing time in PP and MM

2008-12-29T02:47:00.000-08:00

I have one material number that is procured externally but also produced inhouse. Now I have one problem with the GR processing time. As far as I can see the parameter on the material master on MRP2 view and Purchasing view is the same (MARC-WEBAZ). But in my case the GR processing time should be only used for goods receipts in MM (from purchase oders). This GR processing time must not be added to my lead time scheduled in production (when producing the material). How to solve this conflict?

We have a make to order enviroment, that means our production orders are created (and scheduled) directly from the sales order. The sales gets back a confirmed date and quantity from production order scheduling - and here this GR processing time is also added. Absolutely useless in this scenario, but MM needs this GR processing time for the external procurement of the material.

I'm hearing at least two problems here. Let me lumber through them as I see them.

#1 - We have a make to order enviroment, that means our production orders are created (and scheduled) directly from the sales order. The sales gets back a confirmed date and quantity from production order scheduling - and here this GR processing time is also added. Absolutely useless in this scenario, but MM needs this GR processing time for the external procurement of the material.

The GR processing time is quite legitimate, and needful. It represents the time it takes once a material is 'delivered', before it is usable. If that is instantaneous for you, then this field is blank. In fact if it is less than one day, the field should be blank. (MARC-WEBAZ) If you DO have to do testing or documentation or even just 'checking' to be sure the proper certificates
have arrived with this material, then it's nice to have a day here for this. --- I may have overlooked one thing, if you are ONLY thinking of the FERT that your customer ordered, then maybe this field seems trivial. However, if your process requires that the FERT be purchased from some other company (or even supplied from within YOUR company), then there IS a receiving process that has to happen . . . it does take time to back a truck up, get a fork truck to unload it, the
identification process, and then relocating the item to where it can be shipped to your customer.

Also, if you produce this item, then there are 'other' items that need to be 'built' into this item . . . THEY need the GR field, even if you produce the saleable item, it has to be 'received' from production into inventory for you to ship it out.

There is another field that should be considered. This is the procurement lead time. The time it takes for purchasing to "react" to the requirement. When the sales order is placed, the signal will come for 'purchasing' to occur (via MRP perhaps). Purchasing MAY take as long as a day to get that order to a vendor where the vendor can now react. This time is generally a 'standard' time for any given plant/purchasing org and is included using OMDT.

Thirdly, the vendor lead time has to be considered. This is what the field "Planned delivery time" (MARC-PLIFZ) is about. The vendor's turn around time - from the time they are notified of your intention (via a PO perhaps), until they can put it on your dock . . . that is what this field is about. And MRP knows the difference between this field and the others. Between the three fields mentioned, the 'purchased' item is properly planned for . . . except for the exceptions and the fact that this is all based on "norms" and averages which never seem to be exactly what is needed, but that's another discussion .

Next we think of the situation where the item requested is produced by us. In this case (as mentioned before), the GR is STILL legitimate - perhaps not needed if it takes less than a day for your company to receive material from production, inspect it, certify it, and load it up.

However, a "0" is a legitimate entry to this field.

What is also needed is a place to locate the time for "producing" this item. That is where there are options. One option in MRP 2 is the field "in-house production" (MARC-DZEIT). This is sometimes useful, but dangerous. It assumes that no matter how large an order is or how much of a material is needed, it can always be produced in the same period (in 'days', of course). The number of days fits in this field.

If that doesn't 'do it' for you, you can go to the "Work Scheduling" view of the Material Master and include the details for the fields under the "in house production time in days" grouping (Setup time; Interoperation; Processing time; and base quantity). At LEAST this gives the system a 'shot' at planning longer times for greater quantities. If you fill both data points in (in
house production time and " in days, the 'in days' will supercede the other).

Now you've put in all the data that you HAVE to input to have the system plan the length of time needed for telling your customer when you will have their product ready for them.

In the case of your conflict where you produce OR source the item, then you MAY have a problem with GR - look at both scenarios and see what your entry should be. You CAN use the Total Replenishment Leadtime (MARC-WZEIT) field to be the TOTAL TIME when producing the material in-house, because the external replenishment does not look at this field. So MRP will run and depending on how you have it set, it will consider purchasing the material, or making the material, and the fields we've mentioned will impact the result as mentioned.

SAP Factory Calendar

2008-12-29T02:46:00.000-08:00

Factory calendar contain company specific dates such as alternate working Saturdays, Plant shutdown etc.

You can create your company factory calendar via transaction code 'SCAL'.

Assignment of the factory calendar by plant is done in transaction code 'SM30 - V_T001W'.

An example of a SAP application that uses the factory calendar is the SAP MRP modules.

Assuming that you have a specified an alternate working Saturday, MRP will postponed the planned orders to the next working day if it happened to falls on a non-working Saturday.

Difference between MRP vs MPS

2008-12-29T02:44:00.000-08:00

Explain the difference between MRP & MPS. Though both components gives you the requirement list, what we gain out of MPS run rather than running MRP. What is the main idea behind this?

The following might help in explaining the difference between MPS and its counter part MRP.

Master Production Schedule (MPS) :
MPS operates within only one level of the BOM, While MRP can be utilized throughout all levels of a material’s BOM. If a MPS is run on a material, the necessary orders are planned at that level. Dependent requirements (if any) are placed on the next BOM level down, and then the process stops.

Main Idea : Master production scheduling (MPS) is a form of MRP that concentrates planning on the parts or products that have the great influence on company profits or which dominate the entire production process by taking critical resources. These items are marked as ‘A’ parts (MPS items) and are planned with extra attention. These items are selected for a separate MPS run that takes place before the MRP run. The MPS run is conducted without a BOM explosion so that the MRP controller can ensure that the Master schedule items (MSI) are correctly planned before the detailed MRP run takes place.

The master production schedule is a line on the master schedule grid that reflects the anticipated build schedule for those items assigned to the master scheduler. The master scheduler maintains this schedule, and in turn, it becomes a set of planning numbers that drives material requirements planning. It represents what the company plans to produce expressed in specific configurations, quantities, and dates. The master production schedule is not a sales item forecast that represents a statement of demand. The master production schedule must take into account the forecast, the production plan, and other important considerations such as backlog, availability of material, availability of capacity, and management policies and goals. Syn: master schedule.

Material Requirements Planning (MRP) :
A set of techniques that uses bill of material data, inventory data, and the master production schedule to calculate requirements for materials. It makes recommendations to release replenishment orders for material. Further, because it is time-phased, it makes recommendations to reschedule open orders when due dates and need dates are not in phase. Time-phased MRP begins with the items listed on the MPS and determines

(1) the quantity of all components and materials required to fabricate those items and

(2) the date that the components and material are required. Time-phased MRP is accomplished by exploding the bill of material, adjusting for inventory quantities on hand or on order, and offsetting the net requirements by the appropriate lead times.

MRP Interview Questions:

What is the need of mrp list if stock requirement list is already there?

The MRP list displays the result of the last planning run. Changes that have occurred between planning runs are ignored in the MRP list. In contrast to this, the system displays all changes in stock, receipts and issues, which have currently occurred, in the stock/requirements list.

Which tcode are used to run MRP?

- MD01 is generally used to run the MRP for all the materials in a plant normally just before go-live.
- MD02 is used to run MRP for materials which have a BOM i.e multi-level.
- MD03 is used to run MRP for materials which do not have a BOM i.e single level.

Why used Planning tools like APO or I2?

2008-12-29T02:41:00.000-08:00

APO and I2 are Finite PLANNING tools. When MRP runs with APO or I2 (or Red Pepper or Manugistics), it takes Capacity issues into consideration. MRP in SAP R/3 Core does not, it assumes infinite capacity available. (MRP only looks at material availablity.)

However, SAP R/3 DOES do finite SCHEDULING, which is where the system 'dispatches" operations on a production order until it fills up the capacity available, then moves to the next time period and dispatches until that period is filled up. In SAP speak, that is called capacity leveling.

I believe APO should only be used in very large companies (billions) because of the amount of master data that must be maintained, and that data better be ACURATE, or you've wasted a heck of a lot of time. By the way, APO stands for Advanced Planner and Optimizer tool, obviously a German sort of name!

Differences between planning and scheduling, finite and infinite

R/3 does planning without consideration for capacity situations. So if MRP says you need 500 parts on 3/1/04, it schedules them all to be built at the same time, even though you can only do 100 at a time. Assume you have a fixed lot size of 100, you'll get 5 planned orders for 100 to start on the same day. This is "Infinite Planning". APO would recognize that constraint, and instead schedule out the 5 orders over time. The important part of that is that it also will schedule out the deliveries of the components for 5 different days. This is "Finite Planning".

Now, assume old fashion MRP. It schedules all 5 orders for the same day, and the buyers go out an get all of the components for the same day. Then the planner realizes he can't do all 5, and manually changes the schedule, and manually spreads out the 5 orders. The buyers will recieve rescheduling notifications, but not until the scheduler does the manual rescheduling. You could call this "Infinite Scheduling", but that only means the same thing as Infinite Planning.

But, SAP has "Capacity Leveling". What that means is you run another program after MRP (CM27 and CM28), which can be run in batch mode overnight. (There is a ton of configuration and thinking that will be required to do this!). The capacity leveling program will recognize the constrant at the work center level, and fill up the first day, then re-schedule the next order to the next available capacity, then the next order searches for available capacity, and so on. This is called "Finite Scheduling". The problem with this is the opposite of Infinite Planning, which is it doesn't take Material availablity into consideration! The system will re-schedule a production order without thinking about whether the materials will be available or not.

Finite Planning does Finite Sheduling at the same time. If there is no capacity available on the desired date, the system looks for when capacity IS available. Then it stops to see if Materials will also be available (usually based on the lead-time for those components). If there is a material problem, then the system figures out when the materials WILL be available, and then
checks to see if capacity is available on THAT day, and if so, it blocks off capacity, and allocates the materials for that day.

The Concept Of MRP In ERP ERP SAP Modules ==> PP In SAP

2008-12-29T02:38:00.000-08:00

The Concept Of MRP in SAP

MRP in brief :

MRP is the planning tool in SAP which will look at all aspects of a material and is highly based upon the master data of the material. MRP looks at current inventory, current requirements, open purchase req/orders and so on. So if a material is required to satisfy a sales order and there is no inventory, MRP will create a planned order if the item is to be produced in house. This planned order can then be converted to a production order by the master scheduler. If the item is to be procured, then MRP will create a purchase req which the Buyer will convert to a purchase order. This is just one scenario, the system is highly configurable and will do pretty much whatever you tell based on config and master data.

Consumption based planning

- Reorder planning
- Forecast based planning
- Time phased planning

Details of re-order planning
Our motive is to maintain optimum stock level of all the material included in the resource planning. so in this user or system sets a particular quantity of stock as reorder point . Whenever stock quantity fall below this point(reorder point) mrp comes into action and generates procurement proposals according to the settings done in implementation guide

MRP run procedure

1. Create requirement or demand in MD61
2. MRP run by MD02 for a single material
3. See the result in stock requirement list in MD04.

MRP run we can carry out by

1. MD02 - single item multi level
2 .MD03 - single item single level
3 .MD01 - Total planning
4. MD04 Check MRP
5. MD05 MRP lists

For PP, you require following Master Data

1. Material master (MM01)
2. BOM (CS01)
3. Routing (CA01)
4. Work Center (CR01)
5. CK11N / CK40N - Cost Estimate

Production Cycle: -

1. PIR (Planned Independent Reqmt. - MD61)
2. MD02 - MRP Run
3. MD04 - Stock Requirement List
4. CO40 - Convert Planned Orders to Production Order OR CO01 - Create Production Order
5. Here in Production Order - Schedule Order, Release order
6. MIGO / MB1A - Goods Issue against Order (Mvmt Type 261)
7. CO11N - Production Operation confirmation
8. MIGO / MB31 - GR against Prd order
9. CO02 - Technical completion of order
10. KO88 - Order Settlement

Get help for your SAP PP Problems
SAP PP Forum - Do you have a SAP PP Question?

SAP Production Planning Books
SAP PP Certification, Interview Questions and Configuration Books

SAP PP Tips
SAP PP Tips and Production Planning/Control Discussion Forum

Other Logistics Modules

Table of the Order Production Operation

2008-12-29T02:37:00.000-08:00

Which is the table of the order production operation details? I need to get the activities for production order :
Setup, Labor, Machine, Confirmed and to confirm.
I can see look at this in CO02 / Operation Overview (f5) / Operation Detalis / Qty-Activities

That is probably the hardest information to piece together, I used 5 tables with multiple joins to get User Fields for operations in a production order. Maybe you can use something simular.

AFKO - this is for your basic production header info - order number, basic finish date etc

S022 - this is for your operation header details - operation number, Work centre etc if you are only after the header details such as setup time and execution time, you can probably stop here without going to AFVC or AUFV (you definitely need AUFK if you want order status)

AUFK - this is for your order master data - Order released flag, order complete flag, technically complete date, you'll need this to filter out closed orders

AFVC - this is to link to the detail table - however I used the control key field in it so I would know whether it was a MILE stone or GPP1 for confirmation's sake

AUFV - this is the user field table - you may want to replace this with whatever detail you are after

Delete all the automatic joins:

AFKO -> AUFK on:
AUFNR -> AUFNR

AFKO -> S022 on:
AUFNR -> AUFNR
PLNBEZ -> MATNR

AFKO -> AFVC on:
AUFPL -> AUFPL

S022 -> AFVC on:
WERKS -> WERKS
PLNFL -> PLNFL
VORNR -> VORNR

The join below is for user fields in operation detail, you will have to find your own relevant table, but I assume the two key fields will be the same??

AFVC -> AFVU on:
AUFPL -> AUFPL - Routing number of operations in the order APLZL -> APLZL - General Counter for order

SAP PP Master Data Tables

2008-12-29T02:36:00.000-08:00

MASTER DATA

Engineering Change Management
AENR Customer and priority
AEOI Revision Numbers

Work Center
CRHD Workcenter Header Data
CRCA Workcenter Capacity Allocation
CRCO Workcenter Cost Center Assignment
CRHH Hierarchy Header
CRHS Hierarchy Structure
CRTX Workcenter Text
KAKO Capacity Header
KAZY Intervals of Capacity

Routing
PLPO Routing Operation Details
PLKO Routing Header Details
MAPL Routing Link to Material
PLAB Relationships - Standard Network
PLAS Task List - Selection of Operations
PLMZ Component Allocation
PLPH CAPP Sub-operations
PLFH PRT Allocation
PLWP Maintenance Package Allocation
PLMK Inspection Characteristics

Bill of Material
STPO BOM Item Details
STPU BOM Sub Items (designators)
STKO BOM Header Details
MAST BOM Group to Material
STZU BOM History Records
STAS BOM Item Selection
STPF BOM Explosion Structure

Line Design
LDLH Line Hierarchy Header
LDLP Line Hierarchy Items
LDLT Line Hierarchy Takt Times
LDLBC Takts/No. Individual Capacities per Line
LDLBH Line Balance Header
LDLBP Line Balance Items
LDLBT Line Hierarchy Entry and Exit Takts

PRT's
CRFH PRT Master Data
CRVD_A Link of PRT to Document
CRVD_B Link of Document to PRT
CRVE_A Assignment of PRT data to Equipment
CRVE_B Assignment of equipment to PRT data
CRVM_A Link of PRT data to Material
CRVM_B Link of Material to PRT data
CRVS_A Link of PRT Internal number to PRT External number
CRVS_B Link of PRT External number to PRT Internal number

How to create a query that is very similar to CA03?
What tables contain those information and what are the relationships?

See below routing table relationships:

Table MAPL, pass input material number, plant, routing group counter.

Table PLKO, field PLNNR, PLNAL eq mapl-plnnr, mapl-plnal

Table PLAS, field PLNNR, PLNAL eq mapl-plnnr, mapl-plnal and LOEKZ ne ' ', take field PLNKN

Table PLPO, field PLNNR, PLNKN eq plas-plnnr, plas-plnkn

You will get correct result same as CA03 list.

SAP Production Planning Table

2008-12-29T02:35:00.000-08:00

Demand Management
PBED Independent Requirements Data
PBIM Independent Requirements by Material

Repetitive Manufacturing
SAFK RS Header Master Data
S025 LIS -- Run Schedule Quantities
S026 LIS -- Material Usage
S028 LIS -- Reporting Point Statistics
CEZP Reporting Point Document Logs
CPZP Reporting Points - Periodic Totals

MRP Records
MDKP MRP Document Header Data
MDTB MRP Table Structure (no data)
PLSC Planning Scenario (Long-term Planning)
MDFD MRP Firming Dates
MDVM Planning File Entries
S094 LIS -- Stock/Requirements Analysis

Reservations
RESB Reservations/Dependent Requirements

Planned Orders
PLAF Planned Orders

Discrete Production
AFKO Order Header
AFPO Order Item Detail
AFVC Order Operations Detail
AFFL Order Sequence Details
AFFH Order PRT Assignment
AFBP Order Batch Print Requests
AFRU Order Completion Confirmations
AFFW Confirmations -- Goods Movements with Errors
AFRC Confirmations -- Incorrect Cost Calculations
AFRD Confirmations -- Defaults for Collective Confirmation
AFRH Confirmations -- Header Info for Confirmation Pool
AFRV Confirmation Pool
AFWI Confirmations -- Subsequently Posted Goods Movements

Classification
KLAH Class Detail
CABN Characteristic Detail
AUSP Characteristic Values
CAWN Characteristic Values
CAWNT Characteristic Value Texts
KSML Characteristic Allocation to Class
KSSK Material Allocation to Class

Commonly Used Tcodes in PP Module Part 3

2008-12-29T02:33:00.000-08:00

Material Requirement Planning
Menu Nodes           TransactionActivity

Master Data          MD25       Create planning calendar
                     MD26       Change planning calendar
                     MD27       Display planning calendar
                     MDSA       Display BOM explosion number
                     MDSP       Edit BOM explosion number
                     MEQ1       Maintain quota file
                     OPPP       Explode BOM by date
                     MDUS       Display project assignment
                     MDUP       Process project assignment
                     MDL1       Create production lot
                     MDL2       Change production lot
                     MDL3       Display production lot

Planning             MD20       Create planning file entry
                     MD21       Display planning file entry
                     MDAB       Set up planning file entry in background
                     MDRE       Check planning file entry
                     MD01       Total planning online
                     MDBT       Total planning in background
                     MD03       Single-item, single-level planning
                     MD02       Single-item, multi-level planning
                     MD43       Interactive single-item planning
                     MD50       Multi-level, make-to-order planning
                     MD51       Multi-level project planning
                     MF52       Display planning table
                     MF50       Change planning table
                     MF57       Planning table by MRP lists
                     MF51       Planning table by production list

Evaluations          MD04       Stock/requirements list
                     MD07       Collective access of stock/requirements lis
                     MD05       MRP list
                     MD06       Collective access of MRP lists
                     MDLD       Print MRP list
                     MD45       Planning result
                     MD46       Collective access of planning result
                     MD44       Planning situation for a material
                     MD47       Planning situation for a product group
                     MD48       Cross-plant planning situation
                     MD4C       Order report
                     MD09       Pegged requirements
                     CO46       Order progress

Planned Order        MD11       Create planned order
                     MD12       Change planned order
                     MD13       Individual access of planned order
                     MD16       Collective access of planned orders
                     MD14       Individual conversion of planned order into
                     MD15       Collective conversion of planned orders int
                     MDUM       Convert planned order into purchase requisi
                     CO40       Convert individual planned order into produ
                     CO41       Collective conversion of planned orders int
                     CO48       Partial conversion of planned order into pr
                     COR7       Individual conversion of planned order into
                     COR7_PC    Collective conversion of planned orders int
                     COR8       Partial conversion of planned order into pr
                     MDVP       Collective availability check
                     MDAC       Execute action for planned order

LONG TERM PLANNING
PALNNING SCENARIO    MS31       CREATE
                     MS32       CHANGE
                     MS33       DISPLAY
PLANNING RUN         MS01       ON LINE
                     MSBT       SA BACKGROUND JOB
                     MS02       SINGLE ITEM - MULTI LEVEL
                     MS03       SINGLE ITEM - SINGLE LEVEL
                     MS50       SINGLE ITEM - SALES ORDER
                     MS51       SINGLE ITEM PLANNING, PROJECT
                     MFSO       PLANNING TABLE

EVALUTIONS           MS05       MRP LIST MATERIAL
                     MS06       MRP LIST COLLECTIVE DISPLAY
                     MSLD       PRINT MRP LIST
                     MS04       STOCK/REQUIREMENTS LIST
                     MS07       STOCK/REQUIREMENT LIST COLLECTIVE DISPLAY
                     MS44       PLANNING SITUATION MATERIAL
                     MS47       SITUATION PRODUCT GROUP

MPS-MASTER SCHEDULE ITEMS
TOTAL PLANNING       MD40       ON LINE
                     MDBS       SA BACKGROUND JOB
                     MD41       SINGLE ITEM - MULTI LEVEL
                     MD42       SINGLE ITEM - SINGLE LEVEL
                     MD43       SINGLE ITEM - INTERACTIVE
                     MD50       SINGLE ITEM - SALES ORDER
                     MD51       SINGLE ITEM PLANNING, PROJECT

*** EVALUTION IS SIMILAR TO MRP
PRODUCTION CONTROL
ORDER - CREATE       CO01       WITH MATERIAL
                     CO07       WITHOUT MATERIAL
                     CO40       FROM PLANNED ORDER
                     CO41       COLLECTIVE CONVERTION OF PLANNED ORDER
                     CO08       FOR SALES ORDER
                     CO10       FOR PROJECT
                     CO02       CHANGE
                     CO03       DISPLAY

CONTROL              MD04       STOCK/REQUIREMENTS LIST
                     COHV       MASS PROCESSING
                     COMAC      COLLECTIVE AVAILABILITY CHECK
                     CO05N      COLLECTIVE RELEASE
                     CO04N      PRINT
                     CO09       AVAILABILITY OVER VIEW

GOODS MOVEMENT       MF65       STOCK TRANSFER FOR RESERVATION

MATERIAL STAGING     MF68       LOG
                     MB1A       GOODS ISSUE
                     MB31       GOODS RECEIPT
                     COWBPACK   PACK MATERIAL

CONFIRMATION         CO1V       TIME TICKET
FOR OPERATION        CO14       DISPLAY
                     CO13       CANCEL
                     CO1L       REQUESTED CONFIRMATIONS
                     CO1P       PREDEFINED PROCESSES

TOOLS-ARCHIVING      CO78       ORDER
                     KOAA       SETTELMENT DOCUMENTS

CAPACITY PLANNING
EVALUTION            CM01       LOAD

WORK CENTER VIEW     CM02       ORDERS
                     CM03       POOL
                     CM04       BACKLOG
                     CM05       OVERLOAD
                     CM07       VARIABLE
EXTENDED EVALUTION   CM50       WORK CENTER VIEW
                     CM51       INDIVIDUAL CAPACITY VIEW
                     CM52       ORDER VIEW
LEVELLING            CM21       PLANNING TABLE (GRAPHICAL)
WORK CENTER VIEW     CM22       PLANNING TABLE (TABULAR)
INDIVIDUAL CAPACITY VCM27       PLANNING TABLE (GRAPHICAL)
                     CM28       PLANNING TABLE (TABULAR)
ORDER VIEW           CM31       PLANNING TABLE (GRAPHICAL)
                     CM32       PLANNING TABLE (TABULAR)
AVAILABLE CAPACITY   CR12       CHANGE
CAPACITY             CR13       DISPLAY
                     OP4A       SHIFT SEQUENCE
                     OP43       FACTORY CALENDER

Where shall we maintain number range for planned orders?

To maintain number range for planned order. Go to:
MM-->CBP-->NUMBER RANGE-->DEFINE NUMBER RANGE FOR PLANNING RUN.
Don't allow External Number Assignment.

What is t.code for planning calendar and factory calendar?

Planning Calendar--MD25
Factory Calender--SCAL

Menu Path
SPRO-->Materials Management-->Master Data-->Maintain Planning
SPRO-->Calendar--md25

SPRO-->General Settings-->Currencies-->Expiring Currencies-->Maintain
SPRO-->Calendar-->SCAL

Commonly Used Tcodes in PP Module Part 2

2008-12-29T02:32:00.000-08:00

SALES AND OPERATIONS PLANNING
PRODUCT GROUP        MC84       CREATE
                     MC86       CHANGE
                     MC85       DISPLAY
GRAPHIC              MC91       PRODUCT GROUP
                     MC92       OVERVIEW
PLANNING             MC81       CREATE
FOR PRODUCT GROUP    MC82       CHANGE
                     MC83       DISPLAY
                     MC75       TRANSFER PG TO PLANNING
FOR MATERIAL         MC87       CREATE
                     MC88       CHANGE
                     MC89       DISPLAY
                     MC74       TRANSFER MATERIALS TO DM
                     MC9K       MATERIAL AVAILABILITY
VERSION MANAGEMENT   MC78       COPY
                     MC80       DELETE
FLEXIBLE PLANNING    MC93       CREATE
PLANNING             MC94       CHANGE
                     MC95       DISPLAY
                     MC9K       MATERIAL AVAILABILITY
TOOLS/PLANNING TYPE  MC8A       CREATE
MACRO                MC8B       CHANGE
                     MC8C       DISPLAY
EVENT                MC64       CREATE
                     MC65       CHANGE
                     MC66       DISPLAY
ROUGH CUT PLANNING   MC35       CREATE
PROFILE              MC36       CHANGE
                     MC37       DISPLAY
ENVIRONMENT          MC90       TRANSFER MATERIALS TO DM
ACTIVITY REQT.       KSPP       TRANSFER TO COST CENTRE
                     KSBL       COST CENTRE OLANNING REPORT
                     KSOP       TRANSFER TO ACTIVITY BASED COSTING
                     CPBL       PLANNING REPORT PROCESSES
                     MC9C       REPORTING
SETTINGS             MC96       FORECAST PROFILE
DISSAGGRIGATION      MC76       BREAKDOWN PG PLAN
                     MC77       DISPLAY PG PLAN
                     MC75       TRANSFER PG TO PLANNING
                     MC74       TRANSFER MATERIALS TO DM

FORECASTING
INDIVIDUAL FORECAST  MP30       EXECUTE
                     MP31       CHANGE
                     MP32       DISPLAY
TOTAL FORECAST       MP38       EXECUTE
                     MP33       REPROCESS
                     MP39       PRINT
                     MPBT       EXECUTE BACKGROUND
                     MPDR       PRINT BACKGROUND

DEMAND MANAGEMENT
PIR                  MD61       CREATE
                     MD62       CHANGE
                     MD63       DISPLAY
                     MD65       REQTS. FOR SCINARIO
                     MD66       COPY SIMULATED DEPENDENT REQT.
                     MD70       COPY TOTAL FORE CAST
EVALUATION           MD73       DISPLAY TOTAL REQT.
                     MD79       EXCELL INTERFACE
                     MD4C       ORDER REPORT
                     MD72       CHARECTERISTICS PLANNING
CUSTOMER REQT.       MD81       CREATE
                     MD82       CHANGE
                     MD83       DISPLAY

REPETITIVE MANUFACTURING
MASTER DATA          C223       PRODUCTION VERTION
PRODUCT COST PLANNING
COSTING RUN          CKMATSEL   CREATE
SELECTION LIST       CKMATCON   Edit
                     CK40N      EDIT COSTING RUN

Commonly Used Tcodes in PP Module Part 1

2008-12-29T02:31:00.000-08:00

MATERIAL
CREATE-GENERAL       MM01       IMMEDIETELY
                     MM11       SCHEDULE
CHANGE               MM02       IMMEDIETELY
                     MM12       SCHEDULE
                     MM13       ACTIVATE
FLAG FOR DELETION    MM06       IMMEDIETELY
                     MM16       SCHEDULE
DISPLAY              MM03       DISPLAY CURRENT
                     MM19       DISPLAY AT KEY DATE
DISPLAY CHANGES      MM04       ACTIVE CHANGES
                     MM14       SCHEDULE CHANGES
                     MM17       MASS MAINTENANCE
                     MMAM       CHANGE MATERIAL TYPE
OTHER                MMBE       STOCK OVERVIEW
                     MMPV       CLOSE PERIOD
                     MMRV       ALLOW POSTING TO
                                PREVIOUS PERIOD
                     MM50       INSTANT MATERIAL VIEW
                     MMSC       ENTER STORAGE LOCATIONS
                     MM60       MATERIAL LIST
ARCHIVING(MATERIAL)  MM71       ARCHIVE/DELETE
                     MM72       DISPLAY ARCHIVE

BILL OF MATERIAL (MATERIAL BOM)
                     CS01       CREATE
                     CS02       CHANGE
                     CS03       DISPLAY
EXTRAS               CS28       ARCHIVING
                     CS20       MASS CHANGES
EVALUATION/BOM       CS11       BOM MULTILEVEL
EXPLOSION/MATERIAL   CS12       STRUCTURE MULTILEVEL
BOM                  CS13       SUMMURISED BOM

WORK CENTRES
                     CR01       CREATE
                     CR02       CHANGE
                     CR03       DISPLAY
                     CA85       REPLACE
CAPACITY             CR11       CREATE
                     CR12       CHANGE
                     CR13       DISPLAY
HIERARCHY            CR21       CREATE
                     CR22       CHANGE
                     CR23       DISPLAY
LINE HIERARCHY       LDB1       CREATE
                     LDB2       CHANGE
                     LDB3       DISPLAY
REPORTING            CR60       W/C INFORMATION SYSTEM
                     CR05       W/C LIST
                     CR06       COST CENTRE ASSIGNMENT
                     CR07       W/C CAPACITIES
                     CR08       W/C HIERARCHY
WHERE USED           CA80       WORK CENTRE
                     CR15       CAPACITY
                     CR10       CHANGE DOCUMENTS
EXTRAS               CR09       STD. TEXTS TASK LIST
                     CR41       ARCHIVING

ROUTING
STAD. ROUTING        CA01       CREATE
                     CA02       CHANGE
                     CA03       DISPLAY
REF. OPERATION SETS  CA11       CREATE
                     CA12       CHANGE
                     CA13       DISPLAY
RATE ROUTING         CA21       CREATE
                     CA22       CHANGE
                     CA23       DISPLAY
REF. RATE ROUTING    CA31       CREATE
                     CA32       CHANGE
                     CA33       DISPLAY
EXTRAS               CA85       REPLACE W/C
MASS CHANGES         CA95       REPLACE REF. OP. SET
                     CA75       REPLACE PRT
DELETE TASK LIST     CA99       WITH ARCHIVING
                     CA98       W/O ARCHIVING
REPORTING            CA80       WORK CENTRE
WHERE USED LIST      CA90       REF. OP. SETS
                     CA70       PRODUCTION RESORCE TOOLS

COST CENTRE
                     OKKP       MAINTAIN CONTROLLING AREA
                     KS01       CREATE COST CENTRE
                     KZS2       CREATE COSTING SHEET
                     KA01       CREATE PRI. COST ELEMENT
                     KA06       CREATE SEC. COST ELEMENT
                     KL01       CREATE ACTIVITY TYPE
                     KP26       ACTIVITY TYPE/PRICE PLANNING

What is the T-Code for trigger point?

CO30 MENUCO30 Standard trigger points
CO31 SAPMCNSM Create standard trigger point
CO32 SAPMCNSM Change standard trigger point
CO33 SAPMCNSM Display standard trigger point

What the tcodes to archieve/delete a material BOM? - by Jia

Look at this option to delete a material BOM

There are two ways of deleting BOMs:
- Using the Delete function.
- Using the Deletion indicator.

If you select the deletion indicator, the BOM is archived in the next reorganization run, and can be deleted if required. In the BOM header, you set the indicator that controls physical deletion after the archiving run. You can still process the BOM within its validity period.This also applies if the deletion indicator is entered with reference to a change number with a valid-from date that is after the date of the next reorganization run

You can use the below mentioned tcodes:
CS25/CS28 Archiving for BOMs
CS26 BOM deletion
CS27 Retrieval of BOMs

Transaction Code To View All SAP Tables

2008-12-29T02:30:00.000-08:00

What is the transaction code to view all SAP (PP) table,or there is some other way to view?

By: Riki Paramita

To browse tables which specified for PP module only, you can use SE16 with a specified application component & sub-component. First, go to SE16, browse the application component (ex : PP), then select the sub-component (ex : PP-SFC, for Production Orders related tables); and all tables within the specified area will be displayed.

In tcode SE16, click the Down Arrow next to the Table Name field:

Then it will pop-up a screen, look at the bottom of the screen:

Then select components by clicking the + sign to open up the sub-compenent you want. For e.g.:

Some important tables within the PP area :

MAST - Material BOM
STKO - BOM Header
STPO - BOM Positions (detail)
MAPL - Assignment for Task Lists to Materials
PLKO - Routing Group Header
PLSO - Routing Group Sequence
PLPO - Routing Group Operations
AFKO - Production Order Header
AFPO -Production Order Position (details)

Related tables in MM area :

MAKT - Material Descriptions
MARA - General Material Data
MARC - Plant Data for Material
MARD - Storage Location Data for Material
MAST - Material to BOM Link

Interview Questions and Anwsers on SAP PP

2008-12-29T02:29:00.000-08:00

1. If you have released Prdn order today and it had gone to shop floor. Next day it was found that there is shortage of material. What will you?
2. How you define Standard Cost and Variable cost in PP?
3. Where can you find Read PP Master in SAP(PP)?
4. What are all the settings done for configuring integration of PP with FICO?

1. Do availability check. You will get missing parts list. Procure those missing parts. Then confirm the production order. One more thing you can do, change customize setting so that user cannot release if parts are missing during order release.

2. Standard cost is the cost which is fixed for a period, variable cost is varying with period. As for example cost of semi finished, finished materials are fixed & cost of raw materials are varied.

3. You will find in master data tab page of production header data overview, CO02 - Read PP Master Data. Also from Functions menu you will get Read PP Master Data. This means that you want the system to re-update the production order with the latest BOM structure.

4. Assigning of Cost center to work center. Assigning Activity type to work center, Standard Cost estimate, Costing Run, Order settlement, Product costing. *-- Chandan Majumdar

---

1. Can MRP be carried out for one particular level of a bom ( Level code : 0001/0002 etc).
Yes it can be done by running for specific materials (Single Material Single Level)

2 How Requiements( PIR,Sles Order, Customer Requirement) are reduced after they are produced?
Reqmts are reduced automatically after Delivery is made to the Particular Order
(In case of Strategy 11, the PIRs are consumed after the GR for Production Order)

3. Can't one material be assigned to more than one operation in a routing?
One material from a BOM CANNOT be assigned to different Operations.
It can be done by defining the material for so many times as required in the BOM

4. How to insert an inspection checkpoint at the end of an operation?
If in process sample is to be defined, assign inspection type 03 in the Material Master.
Then create MICs and assign them in the Routings.
System automatically generates the Inspection Lots

5. Where we have to specify the teardown time in one operation?
Teardown time can be defined as one of the Standard Parameters...

6. How the process time is calculated in a WC when both labour, Machine categories exist?
Scheduling is done based on the Capacity Category we define in the Workcenter

7. How to create opbject dependencies in a BOM FOR A CONFIGURABLE MATERIAL?
Go to Extras -> Object Dependency -> Assign
For this U need to create Characteristics and Class (of Class Type 300) earlier

8. Can any body explain me why work scheduling view is required for semi finished and finished products?
(Because we'll mention all details in MRP views)
A) We need to maintain working scheduling view in order to make that finished or semi finished goods available for
production as we assign production scheduler and production scheduler profile in this view, if not maintained
conversion of planned order to production will not be possible.

SAP PP Test Questions (MCQ)

2008-12-29T02:28:00.000-08:00

1. A plant can be a physical plant or a logical section of a plant

a) Yes b) No.

Ans: a

Storage locations are areas where materials are stored within a plant

a) Yes b) No.

Ans: a

A purchasing organization can buy for a number of plants

a) Yes b) No.

Ans: a

A purchasing group is a sub-set of a purchasing organization

a) Yes b) No.

Ans: a

2. Strategy Group is relevant for Material Requirement Planning

a) True b) False

Ans: a

3. MRP can be caried out at :

a) Plant Level
b) All Routings
c) Single item – single level
d) Single item – multiple level

Ans: a, c, d

4. In Material Requirement Planning

a) Material availability is ensured
b) If shortage exists the corresponding elements are planned
c) Stock transfers are also possible
d) The availability of the components is ensured via dependent requirements

Ans: d

5. With Make – to Stock strategy 10

a) MRP run considers only Sales Orders
b) MRP run considers only PIR
c) MRP run considers both Sales Order & PIR
d) Sales Order can consume PIR

Ans: b

6. The Individual / Collective indicator in the material Master determines

a) Whether a component is procured for a special customer requirement in the individual segment
b) Requirement quantities of dependent materials are grouped together during MRP run
c) The Material Requirement Planning
d) The Special Procurement.

Ans: c

7. ATP – Available to Promise (Availability check)

a) System checks if all issues are covered by existing receipts
b) Checks if receipts’ quantity still available to cover newly received issues

Ans: a

8. Availability Check PIRs

System does not check against PIRs

a) True b) False

Ans: b

No ATP quantities, receipts or stocks are included

a) True b) False

Ans: b

Determines if sufficient PIRs are planned to cover a SO

a) True b) False

Ans: b

9. Consumption based planning is usually used for following materials

a) All A & B Class Materials
b) Materials with smooth consumption pattern.

Ans: b

10. For Planning at Phantom Assembly Level planned orders are created for Phantom assembly

a) True b) False

Ans: b

11. Stock Requirements List gives ___________________ situation of stock requirement for the material

a) Static : of the last MRP Run
b) Dynamic : Existing at current situation

Ans: b

12. Is Sales order A Qty. 15 PC and Sales order B Qty. 25 PC are booked on same date and stock is 0 PC

a) Separate Planned Order for each Sales Order shall be created if individual indicator is set
b) Only one planned order is created if individual indicator is set
c) Separate Planned Order for each Sales Order shall be created if Collective indicator is set
d) Only one planned order is created if Collective indicator is set

Ans: a, d

13. Planning can create the following after MRP run

a) Planned Orders
b) Production Orders
c) Purchase Orders
d) Schedule Lines

Ans: a, b

14. NETCH is

a) Used in Demand Management
b) Key to run MRP for Total horizon
c) Key to run MRP for Total Planning horizon
d) Not related to MRP

Ans: c

15. Regenerative Planning

a) Plans all material for a specified plant
b) Plans all material for a specified plant for total planning horizon
c) Stands practical for the first time planning run

Ans:

Sample Questions on SAP PP

2008-12-29T02:25:00.000-08:00

1. Which is the highest organisational level in SAP

a) Plant b) Client c) Storage Location

Ans: b

2. For Material Master record PP Data which is the highest organisational level

a) Plant b) Client c) Storage Location

Ans: a

3. What is the difference between F1 Help & F4 Help.

a) F1 is for possible values and F4 is for application help
b) F1 is for Application Help and F4 is for Technical Help
c) F1 is for Field Help and F4 is for possible entries.
d) None of the above

Ans: c

4. Variant Configuration is typically used in

a) Make – to – stock Environment
b) Make – to – Order Environment
c) Spare parts Sale
d) Repetitive Manufacturing Environment

Ans: a

5. Configurable Material check for a material is set in _____________

a) Basic Data b) MRP View
c) Sales View d) Classification

Ans:

6. Basic Data screen contains general data such as

a) Material Number
b) Material description
c) Base unit of measure
d) Technical data

Ans: a, b, c

7. Functions of Classification are

a) To find an appropriate object
b) To find similar objects
c) To establish that no appropriate object exists.

Ans:

8. Entering “/o” in command field

a) Ends current transaction
b) Ends the current cession
c) Opens new cession
d) Opens new transaction

Ans:

9. For creating Material Master the following Transaction Code is used :

a) md01
b) mm01
c) me01
d) mc01

Ans: b

10. The unit in which the stock keeping is done in a company is called

a) Stock unit of measure
b) Base unit of measure
c) Unit of issue
d) Purchase unit of measure

Ans: b

11. Batch is

a) Same as material code
b) Partial quantity of material managed separately from other quantity of same material in stock
c) A non reproducible homogeneous unit with unique specifications
d) None of above
e) All of above

Ans: b

12. A _____________________________ is a complete, formally structured list of the components that make up a product or assembly.

Ans:

13. Component in the BOM are allocated to operation in

a) BOM
b) Material Master
c) Routing
d) Work Center

Ans: c

14. BOM contains the following

a) List of Components
b) Qty of Components
c) Operation to which components is attached.
d) Unit of Measure of components

Ans: a, b, d

15. BOMs are always created as

a) Single Level
b) Multi Level
c) Components
d) Along with routings

Ans: a

SAP PP Questions and Answers

2008-12-29T02:24:00.000-08:00

What are the cutover activities followed for PP module?

I am listing some cut over activities to be followed (for PP - Discrete Manufacturing).

Production Planning / Master data:
For Production planning, only master data shall be migrated to SAP. In the 1st Stage, there is no master data. Following is the master data elements relevant for PP:

- Bill of materials
- Routing.
- Work Centres.

Transaction data:
As of the cut off date, ideally there should not be any work in process. All the open production orders should be closed and semi finished goods should be dismantled and should be added to Raw materials. This strategy should be followed for all production orders where lead time to complete the production order is not large.

Since, the production orders are for longer duration and it is not possible to dismantle the product and add it to inventory, following can be the strategy for migrating the data to SAP:

- Create a material master for the work in process and set the standard price as the cost incurred for that product (ie. Work in process)
- Create a bill of material (which will be used only for this production order) including this material and other materials still to be consumed.
- Create Routing for rest of the production process.
- Bring the work in process material into inventory as of the cut off date.
- Create the production orders in SAP for the Work in process and issue materials to production order.

Complete the production process after the cut off date of the project.

Tips by: K.S.Kulkarni

What happens to planned after it has been converted into production order?

When you convert Planned order to Production order. the planned order are offset by production order. Reference of planned order can be seen in the production order.

How to attach a drawing for a material to BOM? Is it possible?

Yes, you can attach a drawing.
First create a document using Transaction Code "CV01N - Create Document".
Attach your drawing in that document.
The system will generate a document number. Assign this document in the BOM with item category D.

Report in Long Term Planning - You use long term planning for your customers, what they need are very simple, just to calculate future requirements for 1 or 2 years.
Are there any reports in SAP to list of material requirement from LTP?
You need a list of material requirement from long term planning result for each item.

Use MS70 then use MCEC.

Scheduling planned order - How can you get planned orders scheduled so that you can do capacity leveling?
MD11 and then Schedule works fine but ideally you would want the the planned order scheduled automatically on creation? You have tried setting up an action to schedule the orders but cannot get that to work either.

When running MRP, try selecting "2" in the scheduling box this will bring planned orders into CM01 and CM21

Capacity planning CM01 - When you run capacity planning T-code: CM01, you found the plan orders are not included in the pegged requirement, you checked the profile, the check box for order and plan order are all actived.

Guess that planned orders have been created without capacity requirement indicator in MRP ("2" - Lead Time scheduling), if this is the case, then when converted to process orders they will have impact on the Resource. If you want to see them as planned orders, re-run the MRP or change in every planned order, going to the Menu: Edit --> Scheduling

Another couple of possibilities are to do with the routing/work centres used and whether it isactually calculates consumption of capacity of the category at the work centre being displayed in CM01 (it might consume a capacity pool or it might not consume the category).

MPS in Backgound/Online - You want to run MPS for a plant either online or in the background, but you do not get any results. If you run MPS for a single material/plant, then everything is 100% OK.

You need to run a planning file and a consistency check first, transaction OMDO and MDRE respectively you'll need to set up two jobs to do it but it is straight forward, once you've done this set up the background job for MPS to run and do it in NEUPL first time round and then change to NETCH after that.

What is the output of MPS run?

From MPS run you plan the materials which are of 'A' type in the abc analysis (80% dollar value) that have to be planned before hand.
MPS is also a type of MRP only in which components just below the materials on which MPS run is taken place, are planned.

Table for production order status - What is the table for finding status (for Ex TECO ed prodn orders). We are not able to find from AFKO and AFRU tables the status of production orders or at least the link tables if known can be mentionned. You are unable to link the structure caufvd and IOHEADER WITH AFKO and AFRU.

JEST is the table.

Data dictonary table for SOP planning data - You are using Standard SOP (Info structure S076), in which table can you see the planning values that you maintained in MC93 transaction?
You looked under table "S076" and did not see any values there.

Use T.Code MC95 to display your entries under the version which maintained the the table S076.

Production order operation's component allocation - How does SAP know that an operation has components as indicated by the component allocation indicator? Tcode CO08.

Component allocation is done via routing maintenance or BOM maintenance for the assembly. This is master data maintenance. As soon as a PO is created, the master data is read into the PO.

How to delete groups of products?
How to delete a group of products that was created in screen MC84?

Delete the members in the product group and then archive the product group in transaction SARA, object=MM_MATNR.
(The product group is created as a material master record with material type PROD and this record is deleted in SARA.)

SAP PP Self Test Certification Questions

2008-12-29T02:22:00.000-08:00

1. Following are valid BOM categories

a) Inspection BOM
b) Material BOM
c) Equipment BOM
d) Costing BOM

Ans : b, c, d

2. Material BOM that is created without plant is called______________

a) Reference BOM
b) Master BOM
c) Group BOM
d) Master group

Ans: c

3. If a Header Material is used as a BOM item in the same BOM the BOM is referred as ___

a) Repetitive BOM
b) Alternative BOM
c) Multiple BOM
d) Flexible BOM
e) Recursive BOM

Ans:

4. Alternative BOMs are grouped under one internal number and are called__________

a) Multiple BOM
b) Variant BOM
c) Variable BOM
d) Super BOM
e) Header BOM

Ans:

5. BOM can be used for the following

a) MRP
b) Costing
c) Inspection data
d) Sales & Distribution

Ans: a, b, c, d

6. The base quantity in the BOM specifies

a) To which amount of the semi finished product the item quantities refer
b) To which amount the item quantities required for two or more finished products
c) To which amount of the finished product the item quantities refer
d) To which amount the item quantities are not calculated.

Ans: a, b, c

7. Work Center is used in

a) Routing
b) BOM
c) Material Master
d) Inspection Plans

Ans: a, d

8. Routing contains information on the following

a) Material Components
b) Operations
c) Capacity for Work Centers
d) Inspection Characteristics

Ans: a, b, c

9. Alternative sequences in routing are created with reference to

a) Parallel Sequence
b) Master Sequence
c) Standard Sequence
d) Reference Sequence

Ans:

10. Work Center requires formulas for the following

a) Move time
b) Scheduling
c) Capacity requirements
d) Cost estimate using activities

Ans:

11. Routings are identified by ____________________

a) Routing Group
b) Routing Status
c) Group Counter Values
d) Routing Group and Group Counter Values
e) Status and use

Ans:

12. You can assign work center to only one cost center in a time period.

a) True b) False

Ans:

13. Production Planning Module is integrated with the following modules.

a) Material Management
b) Controlling
c) Quality Management
d) Sales & Distribution

Ans: a, b, c, d

14. Movement Type for Goods Receipt in to Ware House

a) 122 b) 123 c) 101 d) 102

Ans: c

15. Movement Type for Transfer Posting to storage location

a) 261 b) 301 c) 311 d) 305

Ans: c

SAP PP Certification Sample Questions

2008-12-29T02:17:00.000-08:00

Caution: more than one answer may be correct.
Please mark ALL correct answers.

Question:
The following control parameters can be set in a long-term planning scenario :

A Planning period
B Opening stock
C Strategy group
D MRP type
E Version of available capacity

Question:
What is the name of the planning level for the MRP run?

A. SOP
B. MP
C. MRP
D. COPA

Question:
What are the main features of the MRP types 'PD' or 'VB'?

A. 'PD' can only be used with 'Net Change Planning'
B. 'VM' can only be used in total planning
C. 'PD' triggers a BOM explosion
D. 'VM' can use the forecast for the calculation of the safety stock

Question:
What is the meaning of the planning time fence?

A. It determines the planning period for the planning run
B. It determines the period in which the planned orders are to be converted into production orders
C. It determines the period in which no automatic changes are to be made to the production plan

Question:
In forecast-based planning, which forecast model does SAP support?

A. dynamic model
B. seasonal trend model
C. split trend model
D. Consumption model

Question:
What conditions must be fulfilled in Customizing if a production order is to be checked for availability?

A. Scope of check
B. Checking group
C. checking rule
D. Checking assignment
E. Inspection period

Answers for SAP PP Certification Sample Questions

Q) Can any body explain me why work scheduling view is required for semi finished and finished products? (Because we'll mention all details in MRP views)

A) We need to maintain working scheduling view in order to make that finished or semi finished goods available for production as we assign production scheduler and production scheduler profile in this view, if not maintained conversion of planned order to production will not be possible.

mySAP Certification - Criteria For Application

2008-12-29T02:12:00.002-08:00

The guidelines: Criteria to applying for a SAP Certification without Prerequisites:

"All candidates registering for the mySAP Certification Test must ensure that they have at least 2 years SAP implementation experience or have attended at least 15 days of relevant training in SAP. It needs to be the classes that SAP Ltd. arrange and accept. For example: HR400 - Payroll Configuration."

Proof of the above must be presented upon registration.

Proof can be given in the following ways:

1. A statement from the Project Manager on Letter Head indicating participant's experience or training.
2. A resume.
3. Certificate of Attendance from the various SAP courses attended.

Terms:
- Candidates must meet criteria mentioned
- Certification enrolment must accompany payment (credit card details preferred) before registration will be processed
- Once payment is received and confirmation provided, cancellation (i.e amendment to dates) is not permitted

Here is a link to check dates of certification:

http://www.sap.com/trainingcatalog -> type in tacert

To find out more about certification test types offered:

http://service.sap.com/certification

- Click on "SAP Consultant Certification"
- Select your relevant certification area

To register:

http://www.sap.com/asia/education/

- Select Registration
- Schedule of test only

To check out SAP Educational terms and conditions:

http://www.sap.com/asia/education/

Quick course search:

http://www.sap.com/trainingcatalog

SAP Certification:

SAP Books on Certification:

Extract the smtp email address

2008-12-29T02:12:00.001-08:00

 Extract the smtp email address from the User Profile SU01 or
* Vendor Master LFA1
*
* Written by : SAP Basis, ABAP Programming and Other IMG Stuff
*              http://www.sap-img.com
*

REPORT ZSMTPADR.

TABLES: USR21,
        LFA1,
        ADR6.

DATA: BEGIN OF WA,
         BNAME      TYPE USR21-BNAME,
         LIFNR      TYPE LFA1-LIFNR,
         ADRNR      TYPE LFA1-ADRNR,
         PERSNUMBER TYPE ADR6-PERSNUMBER,
         ADDRNUMBER TYPE ADR6-ADDRNUMBER,
         SMTP_ADDR  TYPE ADR6-SMTP_ADDR,
      END OF WA,
      ITAB LIKE SORTED TABLE OF WA
                 WITH NON-UNIQUE KEY BNAME LIFNR.

SELECT-OPTIONS: UNAME FOR USR21-BNAME.
SELECT-OPTIONS: LIFNR FOR LFA1-LIFNR.

IF UNAME-LOW <> SPACE.
   SELECT  U~BNAME U~PERSNUMBER U~ADDRNUMBER
           A~SMTP_ADDR
       INTO CORRESPONDING FIELDS OF TABLE ITAB
       FROM ( USR21 AS U
          INNER JOIN ADR6 AS A ON A~PERSNUMBER = U~PERSNUMBER
                              AND A~ADDRNUMBER = U~ADDRNUMBER )
       WHERE U~BNAME IN UNAME.

   LOOP AT ITAB INTO WA.
      WRITE:/ WA-BNAME, WA-SMTP_ADDR(50).
   ENDLOOP.
ENDIF.

IF LIFNR-LOW <> SPACE.
   SELECT  L~LIFNR L~ADRNR
           A~SMTP_ADDR
       INTO CORRESPONDING FIELDS OF TABLE ITAB
       FROM ( LFA1 AS L
          INNER JOIN ADR6 AS A ON A~ADDRNUMBER = L~ADRNR )
       WHERE L~LIFNR IN LIFNR.

    LOOP AT ITAB INTO WA.
       WRITE:/ WA-LIFNR, WA-SMTP_ADDR(50).
    ENDLOOP.
ENDIF.

*-- End of Program

General - Number Range Generation

2008-12-29T02:11:00.000-08:00

* In the 4.6x environment, SAP have included a number range generation
* program just like those used for Purchase Order, Sales Order etc.
*
* This SAP number range generation is an include program.
*
* INCLUDE ZRANGENO.
*
* Always have to be included in the main program data declaration
*
* data: wnorange like INRI-NRRANGENR,            "number range,
*       wsubobj  like inri-SUBOBJECT,            "sub object
*       wdocno(12).
*
* Steps :-
* 1. Number range Sub Object must be maintain in table ZSGRP
*    You can used transaction SE16 to create a table entries.
* 2. Maintain number range and intervals in transaction code SNUM
*
* Written by : SAP Basis, ABAP Programming and Other IMG Stuff
*              http://www.sap-img.com
*

call function 'NUMBER_RANGE_ENQUEUE'
         exporting
               object              = 'ZOWNNO'   "Create with SNUM
         exceptions
               foreign_lock        = 1
               object_not_found    = 2
               system_failure      = 3
               others              = 4.
  if sy-subrc ne 0.
*   message e086 with 'Lock error' sy-subrc.
  endif.

  call function 'NUMBER_GET_NEXT'
         exporting
               nr_range_nr         = wnorange
               object              = 'ZOWNNO'
               subobject           = wsubobj
         importing
               number                  = wdocno  "Number generated by SAP
         exceptions
               interval_not_found      = 1
               number_range_not_intern = 2
               object_not_found        = 3
               quantity_is_0           = 4
               quantity_is_not_1       = 5
               internal_overflow       = 6
               others                  = 7.
  if sy-subrc ne 0.
*   message e086 with 'Number Range' sy-subrc.
  endif.

  call function 'NUMBER_RANGE_DEQUEUE'
    exporting
      object                 = 'ZOWNNO'.

  if sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  endif.

Steps To Implement User Exit CONFPM05

2008-12-29T02:10:00.000-08:00

Real Work Ticket Raise :
We need to perform a user exit for the transaction colln and that exit has to be performed while we save the production order confirmation in colln. Now the concept is as follows: Before we save the confirmation in colln,the user has to check the movement type 261 in transaction mb1a(261 Consumption for order from warehouse) and then save it, once he has done this then the user can go to co11n and save the production confirmation. Now we need to use the user exit in such a way that it has to show an error message while saving the confirmation in co11n if the user has not performed the movement type 261 in transaction mb1a.

By: Donny

Based on your requirements, here's what You have to do :

1. Goto T-Code *CMOD*
2. Enter project name (example : *ZCO11*)
3. Click Create
4. Enter Short text that explain the user exit you want to create (example : "Production order validation").
5. Save, enter the package and TR Number
6. Click *Enhancement assignment*s
7. Enter *CONFPM05* in the input box under title Enhancement
8. Save
9. Click *Components*
10. Double Click *EXIT_SAPLCORF_005*
11. Double click on the word *ZXCOFU05* on *INCLUDE ZXCOFU05*.
12. Just press enter, ignore the Warning message "Program names ZX... are reserved for includes of exit function groups".
13. On the popup question to create include *ZXCOFU05, press Yes. *Enter the appropriate package and TR.
14. The next step is a bit tricky, You have to ask your functional consultant which field on table CAUFV that was updated by performing MB1A, because the user exit only provide 2 structure : CAUFVD_TAB and AFRUD_TAB to be used in the coding.
So the coding should look a little like this (Change the <> and <> with the information from your functional consultant) :
/ if CAUFVD_TAB-<> EQ <>.
message "Error" type 'E'.
endif./

Display Active Exits in a ABAP System

2008-12-29T02:09:00.000-08:00

ZMS_ACTIVE_EXITS - This report shows displays the active exits in a ABAP system along with the corresponding SAP Enhancement (SMOD) and Customer Project (CMOD)

*&---------------------------------------------------------------------*
*& Report ZMS_ACTIVE_EXITS
*&---------------------------------------------------------------------*
*& This report displays all the active customer enhancements in the
*& system and also displays whether they are active or implemented
*&---------------------------------------------------------------------*
REPORT ZMS_ACTIVE_EXITS.
* Data decleration
types: begin of s_function,
fname like MOD0-FUNCNAME,
ftext like tftit-stext,
impl,
active,
example,
end of s_function.
TYPEs : BEGIN OF display_str,
project type modact-name,
enhancement type modact-member,
fm type modsap-member,
status type char20,
END OF display_str.
data : lt_member type table of modact-member,
ls_member like LINE OF lt_member,
lt_fm type table of modsap-member,
ls_fm like LINE OF lt_fm,
lt_modname type table of modact-name,
ls_modname like line of lt_modname,
lt_display type TABLE OF display_str,
ls_display like LINE OF lt_display,
ls_function type s_function,
field1(30).
START-OF-SELECTION.
* Select active customer enhancement.
select name from modattr into ls_modname
where status = 'A'.
append ls_modname to lt_modname.
CLEAR ls_modname.
ENDSELECT.
if lt_modname is INITIAL.
WRITE / 'no active enhancements'.
endif.
* Determine the details about the customer enhancement.
LOOP AT lt_modname INTO ls_modname.
CLEAR : ls_display.
SELECT member from modact into ls_member where name = ls_modname.
select member from modsap into ls_fm where name = ls_member and typ =
'E'.
ls_display-project = ls_modname.
ls_display-enhancement = ls_member.
ls_display-fm = ls_fm.
clear : ls_function.
ls_function-fname = ls_fm.
perform get_impl_status USING ls_function.
if ls_function-impl = 'X'.
ls_display-status = 'Implemented'.
ELSE.
ls_display-status = 'Active'.
endif.
APPEND ls_display to lt_display.
endselect.
ENDSELECT.
ENDLOOP.
* Displaying results
format color = 1.
write : 'Please double-click on the object for follow-on action'.
new-LINE. uline.
write : 'Customer Project', at 30 'SAP Enhancement', at 60 'Exit
Function Modul
e', at 100 'Active/Implemented'.
ULINE.
format color = 0.
loop at lt_display into ls_display.
new-LINE.
write : ls_display-project, at 30 ls_display-enhancement, at 60
ls_displayfm,
at 100 ls_display-status.
ENDLOOP.
* For calling transaction CMOD / SMOD / SE37.
at line-selection.
get cursor field field1.
CASE field1.
WHEN 'LS_DISPLAY-PROJECT'.
set parameter id 'MON_KUN' field sy-lisel(10).
call transaction 'CMOD' and skip first screen.
WHEN 'LS_DISPLAY-ENHANCEMENT'.
set parameter id 'MON' field sy-lisel+29(10).
call transaction 'SMOD' and skip first screen.
WHEN 'LS_DISPLAY-FM'.
set parameter id 'LIB' field sy-lisel+59(30).
call transaction 'SE37' and skip first screen.
WHEN OTHERS.
message 'Click on the right place.' TYPE 'I'.
ENDCASE.
*&---------------------------------------------------------------------*
*& Form get_impl_status
*&---------------------------------------------------------------------*
* This FORM checks whether an EXIT FM is implemented or not
*----------------------------------------------------------------------*
form get_impl_status using p_function type s_function.
data : l_mand LIKE tfdir-mand,
l_incl_names TYPE smod_names OCCURS 1 WITH HEADER LINE.
l_incl_names-itype = 'C'.
APPEND l_incl_names.
CLEAR l_mand.
SELECT SINGLE mand FROM tfdir INTO l_mand WHERE funcname =
p_function-fname.
IF sy-subrc = 0 AND l_mand(1) = 'C'.
p_function-active = 'X'.
* l_status-active = c_true.
ELSE.
p_function-active = ' '.
* l_status-inactive = c_true.
ENDIF.
CALL FUNCTION 'MOD_FUNCTION_INCLUDE'
EXPORTING
funcname = p_function-fname
TABLES
incl_names = l_incl_names
EXCEPTIONS
OTHERS = 4.
IF sy-subrc = 0.
LOOP AT l_incl_names.
SELECT SINGLE name FROM trdir INTO l_incl_names-iname
WHERE name = l_incl_names-iname.
IF sy-subrc = 0.
p_function-impl = 'X'.
ELSE.
p_function-impl = ' '.
ENDIF.
ENDLOOP.
ENDIF.
endform. "get_impl_status

List Of User Exit Related to VL01N

2008-12-29T02:08:00.000-08:00

I need to some restriction in fields ( Actual GI Date, T-Code:Vl01n ).
How do you find out whcih user exits belongs to VL01n ?

Here is the list of user exit related to VL01N :

V02V0001 - Sales area determination for stock transport order
V02V0002 - User exit for storage location determination
V02V0003 - User exit for gate + matl staging area determination
V02V0004 - User Exit for Staging Area Determination (Item)
V50PSTAT - Delivery: Item Status Calculation
V50Q0001 - Delivery Monitor: User Exits for Filling Display Fields
V50R0001 - Collective processing for delivery creation
V50R0002 - Collective processing for delivery creation
V50R0004 - Calculation of Stock for POs for Shipping Due Date List
V50S0001 - User Exits for Delivery Processing
V53C0001 - Rough workload calculation in time per item
V53C0002 - W&S: RWE enhancement - shipping material type/time slot
V53W0001 - User exits for creating picking waves
VMDE0001 - Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 - Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 - Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 - Shipping Interface: Message SDPACK (Packing, Inbound)

Difference Between BADI and User Exits

2008-12-29T02:06:00.002-08:00

Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.

As with customer exits two different views are available:

In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.

In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.

In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.

SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.

The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).

All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.

The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.

What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?

I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.

What is the system landscape?

1) Difference between BADI and USER-EXIT.
i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
ii) BADI's are oops based.

2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
Ex:- 'Development server'-->'Quality server'---> 'Production server'.....

Finding the user-exits of a SAP transaction code

2008-12-29T02:06:00.001-08:00

 Finding the user-exits of a SAP transaction code
*
* Enter the transaction code in which you are looking for the user-exit
* and it will list you the list of user-exits in the transaction code.
* Also a drill down is possible which will help you to branch to SMOD.
*
* Written by : SAP Basis, ABAP Programming and Other IMG Stuff
*              http://www.sap-img.com
*

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

Field exits (SMOD/CMOD) Questions and Answers

2008-12-29T02:05:00.001-08:00

1. Field exit was created with CMOD, but is not processed when calling the screen.

- Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).

- Set profile parameter abap/fieldexit to YES and restart the system.

- After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.

- Do not work on different application servers since there may be some delay before the field exit is activated.

- The profile parameter must be set on all or none of the application servers.

- If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen
number (take care with subscreens).

- Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit use the name of the data element and not the field name.

- After transport, field exits are marked as active but will not be processed.
Tip: First try deactivating the field exit once more and then afterwards, activate it again.

2. How is performance affected by setting abap/fieldexit?

- If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an
update. The user should not notice any difference because screen generation is very fast.

3. Can you read the contents of other screen fields in the field exit?

- In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them
available to other field exits. Note here that field exits are always called and not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.

4. How does the field exit behave on step loop fields ?

- After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system
variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.

5. Can field exits be debugged ?

- No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variable to the file system using TRANSFER... . These can then be analysed there.

6. What can you do if the field contents are no longer transported to to ABAP/4.

- Check whether a value is assigned to the field OUTPUT.

7. When is the field exit called if a conversion exit is attached to the
data element ?

- The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the
ABAP/4 program also receives it.

8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@)

- This is an error in the kernel which no longer occurs as of 3.0C. As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.

9. Field exit is not visible in CMOD, although created.

- If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_. This
function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix,
the data element is not displayed in CMOD.

10. Field exit is not executed although it is active.

- Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an
extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the application by LOOP AT SCREEN.
This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is
invisible.

- Field exits can only be executed for fields that are directly related tothe dictionary. If the relation is indirect, i.e. via an ABAP declaration ( LIKE ), no field exit can be executed.

11. Field exits on check buttons do not work

- Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on
them.

12. Field exits do not work on selection screens

Fast Links:
User Exit Tutorial
A Short Tutorial on User Exits

Get help for your ABAP problems
Do you have a ABAP Question?

SAP Books
SAP Certification, Functional, Basis Administration and ABAP Programming Reference Books

ABAP Tips
ABAP Forum for Discussion and Samples Program Codes for Abapers

What is the difference between SMOD and CMOD?

2008-12-29T02:04:00.001-08:00

CMOD is the Project Management of SAP Enhancements (i.e., SMOD Enhancements). SMOD contains the actual enhancements and CMOD is the grouping of those SMOD enhancements.

User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.

The naming standard of function modules for function module exits is:
EXIT_<3>

The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3>

For Example:

The program for transaction VA01 Create salesorder is SAPMV45A

1. If you search for CALL CUSTOMER-FUNCTION program SAPMV45A you will find ( Among other user exits):

CALL CUSTOMER-FUNCTION '003'
exporting
xvbak = vbak
xvbuk = vbuk
xkomk = tkomk
importing
lvf_subrc = lvf_subrc
tables
xvbfa = xvbfa
xvbap = xvbap
xvbup = xvbup.

The exit calls function module EXIT_SAPMV45A_003

2. How to find user exits

Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT

If you know the Exit name, go to transaction CMOD. Choose menu Utillities->SAP Enhancements.

Enter the exit name and press enter.

You will now come to a screen that shows the function module exits for the exit.

or use this ABAP program to search for user exits :-

Finding the user-exits of a SAP transaction code

3. Using Project management of SAP Enhancements

You want to create a project to enhance transaction VA01

- Go to transaction CMOD
- Create a project called ZVA01
- Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only be used for 1 project. If the enhancement is allready in use, and error message will be displayed
- Press Save
- Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002.
- Double Click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = '2155'.

Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and create a salesorder. Note that Sold-to-party now automatically is "2155"

Do you have a ABAP Question?

What is User Exits and Customer Exits?

2008-12-29T02:02:00.000-08:00

Difference between user exits & customer exits:

User exit - A user exit is a three character code that instructs the system to access a program during system processing.

SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.

UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number

Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks. *-- Mani

The following document is about exits in SAP :-

The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications.

SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.

Types of Exits
There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.

Menu Exits
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.

SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.

Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.

Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.

When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.

Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.

These calls have the following syntax:

CALL CUSTOMER-FUNCTION ‘001’.

Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a company’s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.

The field exit concept lets you create a special function module that contains this logic.

You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.

In 4.6c, you can use "RSMODPRF" program to create field exits.

An example of a user exits :-

MODULE user_exit_0001 INPUT
CASE okcode.
WHEN 'BACK OR EXIT'.
CASE sy-dynnr.
WHEN '100'.
SET SCREEN 0.
LEAVE SCREEN.
WHEN '200'.
******************************************************************************
**** Note that you can write any code that satisfy your needs. ****
**** But in this case, this was wrote as a sample code for reference sake. ****
**** And you can test it. ****
******************************************************************************
SET SCREEN 100.
LEAVE SCREEN.
ENDCASE.
ENDCASE.

A Short Tutorial on User Exits

2008-12-29T02:00:00.000-08:00

Content Author: Abhishek

User exits :

1. Introduction
2. How to find user exits
3. Using Project management of SAP Enhancements

1. Introduction:

User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.

The naming standard of function modules for functionmodule exits is:
EXIT_<3>

The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3>

Example:

The program for transaction VA01 Create salesorder is SAPMV45A

If you search for CALL CUSTOMER-FUNCTION i program
SAPMV45A you will find ( Among other user exits):

CALL CUSTOMER-FUNCTION '003'
exporting
xvbak = vbak
xvbuk = vbuk
xkomk = tkomk
importing
lvf_subrc = lvf_subrc
tables
xvbfa = xvbfa
xvbap = xvbap
xvbup = xvbup.

The exit calls function module EXIT_SAPMV45A_003

2. How to find user exits?

Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT

If you know the Exit name, go to transaction CMOD.

Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.

You will now come to a screen that shows the function module exits for the exit.

3. Using Project management of SAP Enhancements, we want to create a project to enahance trasnaction VA01 .

- Go to transaction CMOD
- Create a project called ZVA01
- Choose the Enhancement assign radio button and press the Change button

In the first column enter V45A0002 Predefine sold-to party in sales document.

Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed

Press Save

Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.

Now the function module is displayed. Double click on include ZXVVAU04 in the function module

Insert the following code into the include: E_KUNNR = '2155'.

Activate the include program. Go back to CMOD and activate the project.

Goto transaction VA01 and craete a salesorder.

Note that Sold-to-party now automatically is "2155"

Create Push Buttons in Application Tool Bar

2008-12-29T01:59:00.000-08:00

How to create pushbuttons in application tool bar in case of selection-screen?

REPORT zsiva_test
MESSAGE-ID zprecot.
TABLES : afru.

TYPES : BEGIN OF ty_test,
ism01 LIKE afru-ism01,
END OF ty_test.
TABLES sscrfields.

SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS : so_werks FOR afru-werks.
SELECTION-SCREEN PUSHBUTTON /79(10) charly USER-COMMAND abcd.
SELECTION-SCREEN END OF BLOCK b1.

INITIALIZATION.
MOVE 'Press' TO charly.

START-OF-SELECTION.

END-OF-SELECTION.

AT SELECTION-SCREEN.
IF sscrfields-ucomm = 'ABCD'.
MESSAGE i000 WITH so_werks-low 'Success' .
ENDIF.

ABAP Clipboard Utilities for Beautiful Commented Code

2008-12-29T01:57:00.000-08:00

 Any fool can write code that a computer can understand.
  Good programmers write code that humans can understand. "
  --- Martin Fowler, Refactoring: Improving the Design of Existing Code


ABAP pretty printer is good for code but not supportive for data declarations.
As a result ABAP code often tends to need more labour to maintain.

I therefore wrote 3 Clipboard utilities

1. YClipJNC based on
   http://sap.ionelburlacu.ro/abap/sap2/Beautify_Source_Code.html
   but improved to include table~column half-line commenting.
   Take any ABAP code (should have survived syntax check) including that "." DOT terminator.
   Copy to Clipboard & F8 on YClipJNC will create the beautiful version in clipboard
   ready for pasting back.

   The big advantage is that you can send for beautification only portions of code
   - this is vital in maintaining someone else's badly written code.

2. YClip2JNC is for Internal Table declarations only, with existing comments
   Aligns everything nicely.

3. YClip3JNC is to create a Commented CALL FUNCTION Pattern.
   Try with "CS_BOM_EXPL_MAT_V2"
   The pattern is ready in clipboard for pasting appropriately.

These 3 utilities should give a big boost to good clean commented ABAP
code.

=========================================================================================

*&---------------------------------------------------------------------*
*&     Beautify ABAP Code Via Clip                                    
*
*&---------------------------------------------------------------------*

* based on ideas from
* http://sap.ionelburlacu.ro/abap/sap2/Beautify_Source_Code.html

* Author Jayanta Narayan Choudhuri
*         Flat 302
*         395 Jodhpur Park
*         Kolkata 700 068
*       Email sss@cal.vsnl.net.in
*       URL:  http://www.geocities.com/ojnc

*-----------------------------------------------------------------------
* This program takes ABAP code in ClipBoard, and does the following:
*    - Attempts to move comments to the end of the line
*    - Adds comments (table name) for the tables listed after a TABLES
*      statement if the line has not been commented already.
*    - Adds comments (field name) for data elements, parameters, and
*      select-options that are defined using the LIKE or FOR statement
*    - For ENDLOOP/ENDSELECT adds comment identify the LOOP/SELECT
*      that is being closed
*    - For FORM/ENDFORM adds comment identify the FORM that is being
*      closed
*    - Calls function PRETTY_PRINTER to do the SAP standard pretty print
*      after the custom comments have been created
* Returns Modified Code Via ClipBoard
*-----------------------------------------------------------------------

REPORT  yclipjnc.          .

TABLES:
   e071 ,      " Change & Transport System: Object Entries of
Requests/Tasks
   tadir ,     " Directory of Repository Objects
   trdir ,     " Generated Table for View TRDIR
   dd02t .     " R/3 DD: SAP table texts

DATA: BEGIN OF mtab_old_prog OCCURS 0,
        line(172) TYPE c,
      END OF mtab_old_prog.

DATA: BEGIN OF mtab_new_prog OCCURS 0,
        line(172) TYPE c,
      END OF mtab_new_prog.

DATA: BEGIN OF mtab_jnc_prog OCCURS 0,
        line(172) TYPE c,
      END OF mtab_jnc_prog.

DATA:
* Hold an entire statement, even if it spans multiple lines
  BEGIN OF mtab_long_line OCCURS 0,
    start        TYPE i,
    end          TYPE i,
    code(9999)   TYPE c, "For type "C", a maximum length specification of 65535 is allowed.
  END OF mtab_long_line.

DATA: BEGIN OF mtab_tabname OCCURS 0,
        tabname LIKE dd02t-tabname,    " Table name
        tabdesc LIKE dd02t-ddtext,     " Short text describing ABAP/4
Dictio
      END OF mtab_tabname.

* Queue to hold list of internal table names for commenting the ENDLOOP
* line
DATA: BEGIN OF mtab_itab_names OCCURS 0,
        tabname(40) TYPE c,
      END OF mtab_itab_names.

* Queue to hold list of table names for commenting the ENDSELECT line
DATA: BEGIN OF mtab_tab_names OCCURS 0,
        tabname(40) TYPE c,
      END OF mtab_tab_names.

DATA: BEGIN OF mtab_form_names OCCURS 0,
        tabname(40) TYPE c,
      END OF mtab_form_names.

DATA: mylength TYPE i,
      myrc     TYPE i.

CONSTANTS: myhats(40) VALUE '^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^'.

* START of EXECUTION

* Read the program code in ClipBoard into an internal table
CALL METHOD cl_gui_frontend_services=>clipboard_import
  IMPORTING
    data   = mtab_old_prog[]
    length = mylength.

IF sy-subrc NE 0.
  WRITE: / `Unable to read ClipBoard`.
  WRITE: / `Exiting program`.
ENDIF.

PERFORM create_condensed_table TABLES mtab_old_prog mtab_long_line.

PERFORM format_program.

CALL FUNCTION `PRETTY_PRINTER`
  EXPORTING
    inctoo             = space
  TABLES
    ntext              = mtab_jnc_prog
    otext              = mtab_new_prog
  EXCEPTIONS
    enqueue_table_full = 1
    include_enqueued   = 2
    include_readerror  = 3
    include_writeerror = 4
    OTHERS             = 5.

* Write the beautiful program code to ClipBoard from internal table
CALL METHOD cl_gui_frontend_services=>clipboard_export
  IMPORTING
    data = mtab_jnc_prog[]
  CHANGING
    rc   = myrc.

LOOP AT mtab_jnc_prog.
  IF mtab_jnc_prog = space.
    SKIP 1.
  ENDIF.
  WRITE: / mtab_jnc_prog.
ENDLOOP.         " LOOP AT MTAB_JNC_PROG


*---------------------------------------------------------------------*
*       FORM CREATE_CONDENSED_TABLE               *
*---------------------------------------------------------------------*
*       Create a table that has all statements condensed onto 1 line  *
*---------------------------------------------------------------------*
FORM create_condensed_table
     TABLES ftab_old_prog STRUCTURE mtab_old_prog
            ftab_long_line STRUCTURE mtab_long_line.

  DATA:
* Structure to hold program code/comment
    BEGIN OF fstr_line,
      code(172)    TYPE c,              " Program Code
      comment(172) TYPE c,              " Inline comments
     END OF fstr_line.

  LOOP AT ftab_old_prog.

    IF ftab_long_line-start = 0.
      ftab_long_line-start = ftab_long_line-end + 1.
      CLEAR ftab_long_line-end.
    ENDIF.

*   Strip off any inline comments so they do not get in the way
*   If comments are not separated, then words in the comments could
*   look like keywords, and cause problems
    SPLIT ftab_old_prog-line AT `"` INTO fstr_line-code fstr_line-comment.

*   Align all statements to be left justified
    SHIFT fstr_line-code LEFT DELETING LEADING space.

*   Put all lines that make up a single statement into one field
*   This will make it easier to isolate key words.  For example, if you
*   want to process a TABLES statement, but exclude the TABLES part of a
*   function call, or a subroutine call.
    CONCATENATE ftab_long_line-code  fstr_line-code
                INTO ftab_long_line-code SEPARATED BY space.

    IF fstr_line-code   CA `.`   OR    " Period means end of statement
       fstr_line-code(1) = `*` OR      " Comment Line
       fstr_line-code   CO space.      " Blank Line
*     Keep track of the table index that the statement ends on
      ftab_long_line-end = sy-tabix.
*     Remove delimiter from concatenation of fields
      SHIFT ftab_long_line-code LEFT BY 1 PLACES.

      APPEND ftab_long_line.

      CLEAR: ftab_long_line-code, ftab_long_line-start.

*     Don`t clear out fstr_long_line-end yet.  It is used to calc
*     fstr_long_line-start.
    ENDIF.

  ENDLOOP.         " LOOP AT FTAB_OLD_PROG
ENDFORM.    " FORM CREATE_CONDENSED_TABLE

*---------------------------------------------------------------------*
*       FORM FORMAT_PROGRAM                                           *
*---------------------------------------------------------------------*
FORM format_program.

  DATA: lstr_old_prog LIKE LINE OF mtab_old_prog.

  LOOP AT mtab_long_line.

    TRANSLATE mtab_long_line-code TO UPPER CASE.

    IF mtab_long_line-code(1) EQ `*`.  " Do not modify Comment Lines

      LOOP AT mtab_old_prog FROM mtab_long_line-start
                            TO   mtab_long_line-end.

        mtab_new_prog-line = mtab_old_prog-line.

        APPEND mtab_new_prog.

      ENDLOOP.     " LOOP AT MTAB_OLD_PROG

    ELSEIF mtab_long_line-code(6) EQ `TABLES`.

*     Reformat any TABLES statements.  Will only reformat when TABLES
*     is at the start of the statement.  Will not try to get table
*     descriptions for CALL FUNCTIONS or FORM/PERFORMs

*     Get the table names from mstr_long_line.
      PERFORM get_table_names_from_statement TABLES mtab_tabname
                                             USING mtab_long_line-code.
*     Find the descriptions for each table
      PERFORM get_table_descriptions TABLES mtab_tabname.

*     create the new statement
      PERFORM build_new_tables_statement USING mtab_long_line.

    ELSE. " All other modifications to the code handled here

      LOOP AT mtab_old_prog FROM mtab_long_line-start
                            TO   mtab_long_line-end.

*       Remove extra spaces from line for comparisons
        lstr_old_prog-line = mtab_old_prog-line.
        CONDENSE lstr_old_prog-line.
        TRANSLATE lstr_old_prog-line TO UPPER CASE.

        IF lstr_old_prog-line CS `"`.  " Comments
          mtab_new_prog-line = mtab_old_prog-line.
        ELSE.
          IF lstr_old_prog-line CS ` LIKE ` OR
             lstr_old_prog-line CS ` TYPE ` OR
             lstr_old_prog-line CS ` FOR `  OR
             lstr_old_prog-line CS `~`.            "jnc OpenSQL

table~column


            PERFORM get_for_like_comment USING mtab_old_prog
                                         CHANGING mtab_new_prog.

          ELSEIF lstr_old_prog-line(8) = 'LOOP AT'.

*     save table name into a queue
            PERFORM enqueue_itab_name USING mtab_long_line-code.
            mtab_new_prog-line = mtab_old_prog-line.

          ELSEIF lstr_old_prog-line(7) = `ENDLOOP`.

*     get name off of queue and add it as a comment to the ENDLOOP line
            PERFORM add_comment_to_endloop USING mtab_old_prog-line
                                           CHANGING mtab_new_prog-line.

          ELSEIF lstr_old_prog-line(7) EQ 'SELECT' AND
                 lstr_old_prog-line(13) NE 'SELECT SINGLE'.

*     save table name into a queue
            PERFORM enqueue_tab_name USING mtab_old_prog-line.
            mtab_new_prog-line = mtab_old_prog-line.
          ELSEIF lstr_old_prog-line(9) = `ENDSELECT`.

*     get name off of queue and add it as a comment to the ENDSELECT
            PERFORM add_comment_to_select USING mtab_old_prog-line
                                          CHANGING mtab_new_prog-line.

          ELSEIF lstr_old_prog-line(5) = 'FORM'.

*         save form name into a queue
            PERFORM enqueue_form_name USING mtab_old_prog-line.
            mtab_new_prog-line = mtab_old_prog-line.

          ELSEIF lstr_old_prog-line(7) = `ENDFORM`.

*         get name off of queue and add it as a comment to the ENDFORM
            PERFORM add_comment_to_endform USING mtab_old_prog-line
                                           CHANGING mtab_new_prog-line.
          ELSE.    " Any other lines
            mtab_new_prog-line = mtab_old_prog-line.
          ENDIF.
        ENDIF.

        APPEND mtab_new_prog.

      ENDLOOP.     " LOOP AT MTAB_OLD_PROG
    ENDIF.
  ENDLOOP.         " LOOP AT MTAB_LONG_LINE

ENDFORM.    " FORM FORMAT_PROGRAM


*---------------------------------------------------------------------*
*       FORM GET_TABLE_NAMES_FROM_STATEMENT                           *
*---------------------------------------------------------------------*
FORM get_table_names_from_statement TABLES ftab_tabname
                                    STRUCTURE mtab_tabname
                                    USING  fc_statement.

  CLEAR ftab_tabname.
  REFRESH ftab_tabname.

  REPLACE `TABLES` WITH space INTO fc_statement.
  TRANSLATE fc_statement USING `. `.   " Replace periods
  TRANSLATE fc_statement USING `, `.   " Replace commas
  TRANSLATE fc_statement USING `: `.   " Replace colons

  CONDENSE fc_statement.               " Remove all extra spaces

  SPLIT fc_statement AT space INTO TABLE ftab_tabname.

ENDFORM.    " FORM GET_TABLE_NAMES_FROM_STATEMENT


*---------------------------------------------------------------------*
*       FORM GET_TABLE_DESCRIPTIONS                                   *
*---------------------------------------------------------------------*
FORM get_table_descriptions TABLES ftab_tabname STRUCTURE mtab_tabname.

  LOOP AT ftab_tabname.
    SELECT SINGLE * FROM  dd02t
           WHERE  tabname     = ftab_tabname-tabname
           AND    ddlanguage  = sy-langu.

    IF sy-subrc = 0.
      ftab_tabname-tabdesc = dd02t-ddtext.
      MODIFY ftab_tabname.
    ENDIF.

  ENDLOOP.         " LOOP AT FTAB_TABNAME
ENDFORM.    " FORM GET_TABLE_DESCRIPTIONS


*---------------------------------------------------------------------*
*       FORM BUILD_NEW_TABLES_STATEMENT                               *
*---------------------------------------------------------------------*
FORM build_new_tables_statement USING fstr_long_line LIKE
mtab_long_line.

  DATA: lc_sep(1)   TYPE c,
        li_rows     TYPE i,
        wordlen     TYPE i.

  DESCRIBE TABLE mtab_tabname LINES li_rows.

  mtab_new_prog-line = `TABLES:`.
  APPEND mtab_new_prog.

  LOOP AT mtab_tabname.
    IF sy-tabix = li_rows.
      lc_sep = `.`.
    ELSE.
      lc_sep = `,`.
    ENDIF.

    wordlen = STRLEN( mtab_tabname-tabname ).

    IF wordlen < 12.
      wordlen = 12 - wordlen.
    ELSE.
      wordlen = 1.
    ENDIF.


    CONCATENATE `^^` mtab_tabname-tabname lc_sep myhats+0(wordlen) ` "
`  mtab_tabname-tabdesc
                                          INTO mtab_new_prog.

    TRANSLATE mtab_new_prog USING `^ `.

    APPEND mtab_new_prog.

  ENDLOOP.         " LOOP AT MTAB_TABNAME

ENDFORM.    " FORM GET_TABLE_DESCRIPTIONS


*---------------------------------------------------------------------*
*       FORM GET_FOR/LIKE_COMMENT                                     *
*---------------------------------------------------------------------*
FORM get_for_like_comment USING value(f_old_prog) LIKE mtab_old_prog
                          CHANGING f_new_prog     LIKE mtab_new_prog
.

  DATA:
    lc_dummy(1)    TYPE c,
    lc_tabname(40) TYPE c,
    wordlen        TYPE i,
    ltab_nametab   LIKE dntab OCCURS 0 WITH HEADER LINE,
    lstr_old_prog  LIKE LINE OF mtab_old_prog,

    BEGIN OF lstr_field,
      tabname      LIKE dd02t-tabname, " Table name
      fldname      LIKE dd02t-tabname, " Table name
    END OF lstr_field.

  lstr_old_prog-line = f_old_prog.  " SAVE input

  TRANSLATE f_old_prog TO UPPER CASE.
  CONDENSE f_old_prog.

  IF f_old_prog-line   CA `"` OR       " Line already commented
     f_old_prog-line(1) = `*`.
    f_new_prog = f_old_prog.
    RETURN.

  ELSEIF f_old_prog CS ` LIKE `.
    SPLIT f_old_prog AT ` LIKE ` INTO lc_dummy lc_tabname.

  ELSEIF f_old_prog CS ` TYPE `.
    SPLIT f_old_prog AT ` TYPE ` INTO lc_dummy lc_tabname.

  ELSEIF f_old_prog CS ` FOR `.
    SPLIT f_old_prog AT ` FOR ` INTO lc_dummy  lc_tabname.

  ELSEIF f_old_prog CS `~`.
    MOVE f_old_prog TO lc_tabname.
    CONDENSE lc_tabname.
    SPLIT lc_tabname AT `~` INTO lstr_field-tabname lstr_field-fldname.

  ELSE.
    f_new_prog = lstr_old_prog-line.
    RETURN.
  ENDIF.

* If there is anything following the table-field in a LIKE or FOR
clause
* it will be removed so that only the table-field remains
  IF NOT f_old_prog CS `~`.
    CONDENSE lc_tabname.

    TRANSLATE lc_tabname USING `. `.     " Remove periods
    TRANSLATE lc_tabname USING `, `.     " Remove commas
    CONDENSE lc_tabname.                 " Remove extra white space

    SPLIT lc_tabname AT `-` INTO lstr_field-tabname lstr_field-fldname.

* The system variables are actually defined in DDIC structure SYST
    IF lstr_field-tabname = `SY`.
      lstr_field-tabname = `SYST`.
    ENDIF.
  ENDIF.

  TRANSLATE lstr_field-tabname TO UPPER CASE.
  TRANSLATE lstr_field-fldname TO UPPER CASE.

  CALL FUNCTION 'NAMETAB_GET'
    EXPORTING
      tabname             = lstr_field-tabname
    TABLES
      nametab             = ltab_nametab
    EXCEPTIONS
      internal_error      = 1
      table_has_no_fields = 2
      table_not_activ     = 3
      no_texts_found      = 4
      OTHERS              = 5.

  IF sy-subrc <> 0.
*    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
*            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.

  READ TABLE ltab_nametab
       WITH KEY tabname   = lstr_field-tabname
                fieldname = lstr_field-fldname.

  IF sy-subrc = 0.

    wordlen = STRLEN( lstr_old_prog-line ).

    IF wordlen < 45.
      wordlen = 45 - wordlen.
    ELSE.
      wordlen = 1.
    ENDIF.

    CONCATENATE lstr_old_prog-line  myhats+0(wordlen) ` " ` ltab_nametab-fieldtext
                            INTO f_new_prog.

    TRANSLATE mtab_new_prog USING `^ `.

  ELSE.
    f_new_prog = lstr_old_prog-line.
  ENDIF.

ENDFORM.    " FORM GET_TABLE_DESCRIPTIONS

*---------------------------------------------------------------------*
*       FORM ENQUEUE_ITAB_NAME                                        *
*---------------------------------------------------------------------*
FORM enqueue_itab_name USING value(f_line) LIKE mtab_long_line-code.

  DATA:
    lc_dummy(1) TYPE c,
    lc_itab(40) TYPE c.

  TRANSLATE f_line TO UPPER CASE.

  SPLIT f_line AT `LOOP AT ` INTO lc_dummy lc_itab.

  SPLIT lc_itab AT space INTO lc_itab lc_dummy.

  TRANSLATE lc_itab USING `. `.
  CONDENSE lc_itab.

  mtab_itab_names = lc_itab.

* Always have the most recent LOOP AT table as the first entry in the
* queue
  INSERT mtab_itab_names INDEX 1.

ENDFORM.    " FORM GET_TABLE_DESCRIPTIONS


*---------------------------------------------------------------------*
*       FORM ADD_COMMENT_TO_ENDLOOP                                   *
*---------------------------------------------------------------------*
FORM add_comment_to_endloop USING fstr_long_line LIKE mtab_old_prog-line
                            CHANGING f_prog_line LIKE mtab_new_prog-line
.

  IF mtab_old_prog-line NA `"`.        " No comments
*     Get the internal table from the queue
    READ TABLE mtab_itab_names INDEX 1.
    CONCATENATE mtab_old_prog-line `    "` `LOOP AT`  mtab_itab_names-tabname
                                   INTO f_prog_line SEPARATED BY space.

*     Dequeue the itab name
    DELETE mtab_itab_names INDEX 1.
  ELSE.
    f_prog_line = mtab_old_prog-line.
  ENDIF.
ENDFORM.    " FORM GET_TABLE_DESCRIPTIONS


*---------------------------------------------------------------------*
*       FORM ENQUEUE_TAB_NAME                                         *
*---------------------------------------------------------------------*
FORM enqueue_tab_name USING  f_line LIKE mtab_old_prog-line.

  DATA:
    lc_dummy(1) TYPE c,
    lc_tab(40) TYPE c.

  TRANSLATE f_line TO UPPER CASE.

  SPLIT f_line AT ` FROM ` INTO lc_dummy lc_tab.

  CONDENSE lc_tab. " Remove leading/trailing extra spaces

  SPLIT lc_tab AT space INTO lc_tab lc_dummy.

  TRANSLATE lc_tab USING `. `.
  CONDENSE lc_tab.

  mtab_tab_names = lc_tab.

* Always have the most recent LOOP AT table as the first entry in the
* queue
  INSERT mtab_tab_names INDEX 1.

ENDFORM.    " FORM GET_TABLE_DESCRIPTIONS


*---------------------------------------------------------------------*
*       FORM ADD_COMMENT_TO_SELECT                                    *
*---------------------------------------------------------------------*
FORM add_comment_to_select USING fstr_long_line LIKE mtab_old_prog-line
    CHANGING f_prog_line.

  IF mtab_old_prog-line NA `"`.        " No comments
*     Get the table from the queue
    READ TABLE mtab_tab_names INDEX 1.
    CONCATENATE mtab_old_prog-line  `    "` `SELECT FROM`
mtab_tab_names-tabname
                                    INTO f_prog_line SEPARATED BY
space.

*     Dequeue the tab name
    DELETE mtab_tab_names INDEX 1.
  ELSE.
    f_prog_line = mtab_old_prog-line.
  ENDIF.

ENDFORM.    " FORM GET_TABLE_DESCRIPTIONS


*---------------------------------------------------------------------*
*       FORM ADD_COMMENT_TO_ENDFORM                                   *
*---------------------------------------------------------------------*
FORM add_comment_to_endform USING fstr_long_line LIKE
mtab_old_prog-line
                            CHANGING f_prog_line.

  IF mtab_old_prog-line NA `"`.        " No comments
*     Get the table from the queue
    READ TABLE mtab_form_names INDEX 1.
    CONCATENATE mtab_old_prog-line `   "` `FORM`  mtab_form_names-tabname
                                   INTO f_prog_line SEPARATED BY space.

*     Dequeue the form name
    DELETE mtab_form_names INDEX 1.
  ELSE.
    f_prog_line = mtab_old_prog-line.
  ENDIF.

ENDFORM.    " FORM GET_TABLE_DESCRIPTIONS


*---------------------------------------------------------------------*
*       FORM ENQUEUE_FORM_NAME                                        *
*---------------------------------------------------------------------*
FORM enqueue_form_name USING f_line.

  DATA:
    lc_dummy(1) TYPE c,
    lc_tab(40) TYPE c.

  TRANSLATE f_line TO UPPER CASE.

  SPLIT f_line AT `FORM ` INTO lc_dummy
           lc_tab.

  CONDENSE lc_tab. " Remove leading/trailing extra spaces

  SPLIT lc_tab AT space INTO lc_tab lc_dummy.

  TRANSLATE lc_tab USING `. `.
  CONDENSE lc_tab.

  mtab_form_names = lc_tab.

* Always have the most recent LOOP AT table as the first entry in the
* queue
  INSERT mtab_form_names INDEX 1.

ENDFORM.    " FORM ENQUEUE_FORM_NAME


=========================================================================================

*&---------------------------------------------------------------------*
*&     Beautify ABAP Code Via Clip                                    
*
*&---------------------------------------------------------------------*

* Author Jayanta Narayan Choudhuri
*         Flat 302
*         395 Jodhpur Park
*         Kolkata 700 068
*       Email sss@cal.vsnl.net.in
*       URL:  http://www.geocities.com/ojnc

*-----------------------------------------------------------------------
* This program takes Structure & internal table declarations in ClipBoard,
* and does prefect alignment as possible
* Returns Modified Code Via ClipBoard
*-----------------------------------------------------------------------

REPORT  yclip2jnc.

DATA: BEGIN OF mtab_old_prog OCCURS 0,
        line(172) TYPE c,
      END OF mtab_old_prog.

DATA: BEGIN OF mtab_new_prog OCCURS 0,
        line(172) TYPE c,
      END OF mtab_new_prog.

DATA: BEGIN OF i_words OCCURS 0,
        word(172) TYPE c,
      END OF i_words.

DATA: wordlen  TYPE i,
      saveix   TYPE i,
      maxlen1  TYPE i,
      maxlen2  TYPE i,
      maxlen3  TYPE i,
      wordoff  TYPE i,
      colnum   TYPE i,
      mylength TYPE i,
      diff     TYPE i,
      myrc     TYPE i,
      workline(172).

CONSTANTS: myhats(40) VALUE '^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^'.

* Read the program code in ClipBoard into an internal table
CALL METHOD cl_gui_frontend_services=>clipboard_import
  IMPORTING
    data   = mtab_old_prog[]
    length = mylength.

IF sy-subrc NE 0.
  WRITE: / `Unable to read ClipBoard`.
  WRITE: / `Exiting program`.
ENDIF.

* SAP pads non-displayable characters in last few lines
LOOP AT  mtab_old_prog.
  MOVE sy-tabix TO saveix.

  CONDENSE mtab_old_prog-line.
  REPLACE ALL OCCURRENCES OF ' ,' IN mtab_old_prog-line WITH ','.

  SPLIT mtab_old_prog-line AT space INTO TABLE i_words.

  LOOP AT i_words.
    wordlen = STRLEN( i_words-word ).
    IF wordlen > 60
    OR i_words-word+0(1) < space
    OR i_words-word+0(1) > '~'.
      DELETE mtab_old_prog INDEX saveix.
      EXIT.
    ENDIF.
  ENDLOOP.
ENDLOOP.

LOOP AT  mtab_old_prog.
  CONDENSE mtab_old_prog-line.
  REPLACE ALL OCCURRENCES OF ' ,' IN mtab_old_prog-line WITH ','.

  SPLIT mtab_old_prog-line AT space INTO TABLE i_words.

  MOVE 1 TO colnum.
  LOOP AT i_words.
    wordlen = STRLEN( i_words-word ).
    CASE colnum.
      WHEN 1.
        IF  wordlen > maxlen1.
          MOVE wordlen TO maxlen1.
        ENDIF.
      WHEN 2.
        IF  wordlen > maxlen2.
          MOVE wordlen TO maxlen2.
        ENDIF.
      WHEN 3.
        IF  wordlen > maxlen3.
          MOVE wordlen TO maxlen3.
        ENDIF.
    ENDCASE.
    ADD 1 TO colnum.
  ENDLOOP.
ENDLOOP.


LOOP AT  mtab_old_prog.
  workline = mtab_old_prog-line.
  CONDENSE workline.
  REPLACE ALL OCCURRENCES OF ' ,' IN mtab_old_prog-line WITH ','.

  SPLIT workline AT space INTO TABLE i_words.

  LOOP AT i_words.
    FIND i_words-word IN mtab_old_prog-line MATCH OFFSET wordoff.
    EXIT.
  ENDLOOP.
  EXIT.
ENDLOOP.

LOOP AT  mtab_old_prog.
  CONDENSE mtab_old_prog-line.
  REPLACE ALL OCCURRENCES OF ' ,' IN mtab_old_prog-line WITH ','.

  SPLIT mtab_old_prog-line AT space INTO TABLE i_words.

  MOVE 1 TO colnum.
  LOOP AT i_words.
    wordlen = STRLEN( i_words-word ).
    CASE colnum.
      WHEN 1.
        PERFORM f_diff_calc USING maxlen1  wordlen
                            CHANGING diff.
        CONCATENATE myhats+0(wordoff) i_words-word myhats+0(diff) INTO
mtab_new_prog-line.
      WHEN 2.
        PERFORM f_diff_calc USING maxlen2  wordlen
                            CHANGING diff.
        CONCATENATE mtab_new_prog-line i_words-word myhats+0(diff) INTO
mtab_new_prog-line.
      WHEN 3.
        PERFORM f_diff_calc USING maxlen3  wordlen
                            CHANGING diff.
        CONCATENATE mtab_new_prog-line i_words-word myhats+0(diff) INTO mtab_new_prog-line.
      WHEN OTHERS.
        CONCATENATE mtab_new_prog-line ` ` i_words-word INTO mtab_new_prog-line.
    ENDCASE.
    ADD 1 TO colnum.
  ENDLOOP.
  TRANSLATE mtab_new_prog-line USING `^ `.
  APPEND mtab_new_prog.
ENDLOOP.

* Write the beautiful program code to ClipBoard from internal table
CALL METHOD cl_gui_frontend_services=>clipboard_export
  IMPORTING
    data = mtab_new_prog[]
  CHANGING
    rc   = myrc.

LOOP AT mtab_new_prog.
  IF mtab_new_prog = space.
    SKIP 1.
  ENDIF.
  WRITE: / mtab_new_prog.
ENDLOOP.         " LOOP AT MTAB_NEW_PROG

*&--------------------------------------------------------------------*
*&      Form  f_diff_calc
*&--------------------------------------------------------------------*
FORM f_diff_calc USING    value(maxlen)  TYPE i
                          value(wordlen) TYPE i
                 CHANGING diff TYPE i.

  COMPUTE diff = maxlen - wordlen + 4.
  IF diff > 40.
    diff = 40.
  ENDIF.
ENDFORM.                    "f_diff_calc


=========================================================================================

*&---------------------------------------------------------------------*
*&     Beautiful Function Module Call via clipboard                   
*
*&---------------------------------------------------------------------*

* Author Jayanta Narayan Choudhuri
*         Flat 302
*         395 Jodhpur Park
*         Kolkata 700 068
*       Email sss@cal.vsnl.net.in
*       URL:  http://www.geocities.com/ojnc

*-----------------------------------------------------------------------
* This program takes a parameter as a Function Module Name
* and does a documented "pattern paste"
* Returns pattern Code Via ClipBoard
*-----------------------------------------------------------------------

PROGRAM yclip3jnc.

TYPE-POOLS : slis.

PARAMETERS: p_func LIKE fupararef-funcname.     " Name of Function Module

DATA : BEGIN OF i_tab OCCURS 0,
        funcname      LIKE    fupararef-funcname,       " Name of Function Module
        paramtype     LIKE    fupararef-paramtype,      " Parameter type
        pposition     LIKE    fupararef-pposition,      " Internal Table, Current Line Index
        optional      LIKE    fupararef-optional,       " Optional parameters
        parameter     LIKE    fupararef-parameter,      " Parameter name
        defaultval    LIKE    fupararef-defaultval,     " Default value for import parameter
        structure     LIKE    fupararef-structure,      " Associated
Type of an Interface Parameter
        stext         LIKE    funct-stext,              " Short text
    END OF i_tab.

DATA: BEGIN OF mtab_new_prog OCCURS 0,
        line(172) TYPE c,
      END OF mtab_new_prog.

DATA: funcdesc LIKE tftit-stext,     " Short text for function module
      mylen    TYPE i,
      myrc     TYPE i.

CONSTANTS: myhats(40) VALUE '^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^'.

TRANSLATE p_func TO UPPER CASE.

SELECT SINGLE
       tftit~stext     " Short text for function module
  INTO funcdesc
  FROM tftit
 WHERE tftit~funcname = p_func
   AND tftit~spras    = sy-langu.

TRANSLATE p_func TO LOWER CASE.

CONCATENATE  `CALL FUNCTION ` p_func  `   " ` funcdesc INTO mtab_new_prog-line.
APPEND mtab_new_prog.

TRANSLATE p_func TO UPPER CASE.

SELECT
       fupararef~funcname      " Name of Function Module
       fupararef~paramtype     " Parameter type
       fupararef~pposition     " Internal Table, Current Line Index
       fupararef~optional      " Optional parameters
       fupararef~parameter     " Parameter name
       fupararef~defaultval    " Default value for import parameter
       fupararef~structure     " Associated Type of an Interface
Parameter
       funct~stext             " Short text
  INTO TABLE i_tab
  FROM fupararef
       INNER JOIN funct
       ON  fupararef~funcname  = funct~funcname
       AND fupararef~parameter = funct~parameter
       AND funct~spras = sy-langu
 WHERE fupararef~funcname = p_func
 AND fupararef~r3state = 'A'
 ORDER BY fupararef~paramtype
          fupararef~pposition.


LOOP AT i_tab.
  AT NEW paramtype.
    CASE i_tab-paramtype.
      WHEN 'C'.
        MOVE '  CHANGING' TO mtab_new_prog-line.
      WHEN 'E'.
        MOVE '  IMPORTING' TO mtab_new_prog-line.
      WHEN 'I'.
        MOVE '  EXPORTING' TO mtab_new_prog-line.
      WHEN 'T'.
        MOVE '  TABLES' TO mtab_new_prog-line.
      WHEN 'X'.
        MOVE '  EXCEPTIONS' TO mtab_new_prog-line.
    ENDCASE.
    APPEND mtab_new_prog.
  ENDAT.

  IF i_tab-optional = 'X'.
    mtab_new_prog-line = `*^^^`.
  ELSE.
    mtab_new_prog-line = `^^^^`.
  ENDIF.

  IF i_tab-paramtype = 'X'.
    MOVE i_tab-pposition TO i_tab-defaultval.
    CONDENSE i_tab-defaultval.
  ELSE.
    TRANSLATE i_tab-parameter TO LOWER CASE.
  ENDIF.

  CONCATENATE mtab_new_prog-line i_tab-parameter '^=^' INTO mtab_new_prog-line.

  IF i_tab-defaultval IS NOT INITIAL.
    CONCATENATE mtab_new_prog-line i_tab-defaultval  INTO mtab_new_prog-line.
  ENDIF.

  mylen = STRLEN( mtab_new_prog-line ).

  IF mylen < 31.
    COMPUTE mylen = 31 - mylen.
  ELSE.
    MOVE 1 TO mylen.
  ENDIF.

  TRANSLATE i_tab-structure TO LOWER CASE.

  CONCATENATE mtab_new_prog-line myhats+0(mylen) ` " ` i_tab-structure INTO mtab_new_prog-line.

  mylen = STRLEN( mtab_new_prog-line ).

  IF mylen < 47.
    COMPUTE mylen = 47 - mylen.
  ELSE.
    MOVE 1 TO mylen.
  ENDIF.

  CONCATENATE mtab_new_prog-line myhats+0(mylen) ` ` i_tab-stext INTO mtab_new_prog-line.

  APPEND  mtab_new_prog.
ENDLOOP.     " LOOP AT I_TAB

CONCATENATE  `    .  "  ` p_func INTO mtab_new_prog-line.
APPEND mtab_new_prog.

LOOP AT mtab_new_prog.
  TRANSLATE mtab_new_prog-line USING `^ `.
  MODIFY mtab_new_prog.

  IF mtab_new_prog = space.
    SKIP 1.
  ENDIF.
  WRITE: / mtab_new_prog.
ENDLOOP.         " LOOP AT MTAB_NEW_PROG

* Write the beautiful program code to ClipBoard from internal table
CALL METHOD cl_gui_frontend_services=>clipboard_export
  IMPORTING
    data = mtab_new_prog[]
  CHANGING
    rc   = myrc.

Recursion with Loop Checking in SAP

2008-12-29T01:56:00.000-08:00

 This program can be a model for any ABAP recursion.
* This is often needed to navigate down hierarchical data.
* One example is BOM.

* Important point is to chack for stack overflow
* and give RIGHT MESSAGE so that corrective action can be taken.

*&---------------------------------------------------------------------*
* Sample Program Showing Recursion in ABAP
* Simple BOM Tree walking in ABAP
* Takes Care of Diagnostics as well - detects Loops
* Hence never experience Stack Overflow!
*&---------------------------------------------------------------------*

*&---------------------------------------------------------------------*
* http://www.sap-img.com/abap/reincarnation-of-reuse-alv-fieldcatalog-merge.htm
*     has INCLUDE zjncinclude with FORM zjnc_dump_list
*&---------------------------------------------------------------------*

* Author Jayanta Narayan Choudhuri
*         Flat 302
*         395 Jodhpur Park
*         Kolkata 700 068
*       Email sss@cal.vsnl.net.in
*       URL:  http://www.geocities.com/ojnc

REPORT zjncrecursion.

INCLUDE zjncinclude. " From www.sap-img.com

TABLES: makt.

CONSTANTS: maxlevels TYPE i VALUE 10.

TYPES: BEGIN OF ty_usage,
          parent  TYPE  makt-matnr,
          child   TYPE  makt-matnr,
          usage   TYPE  mseg-menge,
       END OF ty_usage.

DATA: wa_usage  TYPE ty_usage,
      it_usage  TYPE STANDARD TABLE OF ty_usage.    " USAGE data

TYPES: BEGIN OF ty_stack,
          level   TYPE  h_level,
          matnr   TYPE  makt-matnr,
          menge   TYPE  mseg-menge,
       END OF ty_stack.

DATA: istackpos TYPE i,
      wa_stack  TYPE ty_stack,
      it_stack  TYPE STANDARD TABLE OF ty_stack.   "BOM Stack

TYPES: BEGIN OF ty_reqd,
          matnr   TYPE  makt-matnr,
          menge   TYPE  mseg-menge,
       END OF ty_reqd.

DATA: wa_reqd   TYPE ty_reqd,
      it_reqd   TYPE STANDARD TABLE OF ty_reqd.    "NET Requirement of
RAW Material

PARAMETERS: p_build TYPE makt-matnr,    "Target   to Build
            p_menge TYPE mseg-menge.    "Quantity to Build

INITIALIZATION.
  PERFORM f_usage_data.


START-OF-SELECTION.

  istackpos = 0.

  MOVE istackpos  TO wa_stack-level.
  MOVE p_build    TO wa_stack-matnr.
  MOVE p_menge    TO wa_stack-menge.
  APPEND wa_stack TO it_stack.                              " 1st PUSH

  PERFORM f_explode USING p_build.

  SORT it_reqd BY matnr.

  PERFORM zjnc_dump_list USING 'IT_REQD' 'WA_REQD' 'Net RAW
Requirement'.

*&--------------------------------------------------------------------*
*&      Form  f_Explode
*&--------------------------------------------------------------------*
FORM f_explode USING p_pmatnr.
  DATA: icount   TYPE i,
        totalreq TYPE mseg-menge.

  istackpos = istackpos + 1.                          " PUSH

  IF istackpos GE maxlevels.
    PERFORM f_dumpstack.    " terminate
    LEAVE PROGRAM.
  ENDIF.

  icount = 0.

  LOOP AT it_usage INTO wa_usage WHERE parent = p_pmatnr.
    icount = icount + 1.

    MOVE istackpos      TO wa_stack-level.
    MOVE wa_usage-child TO wa_stack-matnr.
    MOVE wa_usage-usage TO wa_stack-menge.
    APPEND wa_stack     TO it_stack.                  " PUSH

    PERFORM f_explode USING wa_usage-child.

  ENDLOOP.

  IF icount = 0.                                  " then LEAF
    totalreq = '1.0'.
    LOOP AT it_stack INTO wa_stack.
      totalreq = totalreq * wa_stack-menge.
    ENDLOOP.

    MOVE p_pmatnr   TO wa_reqd-matnr.
    MOVE totalreq   TO wa_reqd-menge.
    COLLECT wa_reqd INTO it_reqd.

  ENDIF.

  DELETE it_stack INDEX istackpos.                      " POP

  istackpos = istackpos - 1.                            " POP

ENDFORM.                    "f_Explode

*&--------------------------------------------------------------------*
*&      Form  f_dumpstack
*&--------------------------------------------------------------------*
FORM f_dumpstack.

  PERFORM zjnc_dump_list USING 'IT_STACK' 'WA_STACK' 'LOOP in BOM
STACK'.

ENDFORM.                    "f_dumpstack

*&--------------------------------------------------------------------*
*&      Form  f_usage_data for Hungry Bengali ABAPer in Kolkata
*&--------------------------------------------------------------------*
FORM f_usage_data.
  MOVE 'FISHCURRY'   TO wa_usage-parent.
  MOVE 'SPICES'      TO wa_usage-child.
  MOVE 10            TO wa_usage-usage.
  APPEND wa_usage TO it_usage.

  MOVE 'FISHCURRY'   TO wa_usage-parent.
  MOVE 'MIRCHI'      TO wa_usage-child.
  MOVE 5             TO wa_usage-usage.
  APPEND wa_usage TO it_usage.

  MOVE 'FISHCURRY'   TO wa_usage-parent.
  MOVE 'ALOO'        TO wa_usage-child.
  MOVE 8             TO wa_usage-usage.
  APPEND wa_usage TO it_usage.

  MOVE 'SPICES'      TO wa_usage-parent.
  MOVE 'MIRCHI'      TO wa_usage-child.
  MOVE 2             TO wa_usage-usage.
  APPEND wa_usage TO it_usage.

  MOVE 'SPICES'      TO wa_usage-parent.
  MOVE 'JEERA'       TO wa_usage-child.
  MOVE 3             TO wa_usage-usage.
  APPEND wa_usage TO it_usage.

  MOVE 'SPICES'      TO wa_usage-parent.
  MOVE 'HALUD'       TO wa_usage-child.
  MOVE 7             TO wa_usage-usage.
  APPEND wa_usage TO it_usage.

ENDFORM.                    "f_usage_data

ABAP Tips by : Jayanta Narayan Choudhuri
Author Email: sss@cal.vsnl.net.in
Author Website: http://www.geocities.com/ojnc

Tree type report in ABAP

2008-12-29T01:53:00.000-08:00

Tree type report in ABAP

With Compliments from: Ravi

REPORT ZRJNTRIAL_TREE LINE-COUNT 65
LINE-SIZE 80
                                               NO STANDARD PAGE
HEADING.
*********************************************************************
DATA: BEGIN OF ITEMS OCCURS 100,
         ID(10),
         PARENT_ID(10),
         TEXT(20),
         SYMBOL,
      END OF ITEMS,
      TABIX_STACK LIKE SY-TABIX OCCURS 10 WITH HEADER LINE,
      ITEMS_SHOW LIKE ITEMS OCCURS 100 WITH HEADER LINE.
INCLUDE .
* append sample items (mixed order)
PERFORM APPEND_ITEM USING:
    '1'  ''        'Food',
    '2'  ''        'Drinks',
    '12' '9'       'Jack Daniels',
    '17' '11'      'Bosch',
    '3'  ''        'Tools',
    '4'  '1'       'Meat',
    '16' '11'      'Metabo',
    '5'  '1'       'Chocolate',
    '6'  '2'       'Alcoholic',
    '8'  '4'       'Pork',
    '10' '5'       'Milka',
    '11' '3'       'Drills',
    '13' '9'       'Jim Beam',
    '7'  '4'       'Beef',
    '14' '2'       'Non-alcoholic',
    '35' '31'      'Teran',
    '9'  '6'       'Whiskey',
    '15' '14'      'Coca-cola',
    '18' '6'       'Wine',
    '28' '18'      'Croatia',
    '33' '28'      'Slavonia',
    '34' '28'      'Istria',
    '29' '18'      'Hungary',
    '30' '29'      'Tokaj',
    '19' '33'      'Enjingi',
    '20' '33'      'Zdjelarevic',
    '22' '19'      'Riesling',
    '23' '19'      'Chardonnay',
    '24' '20'      'Riesling',
    '32' '31'      'Malvazija',
    '25' '20'      'Merlot',
    '31' '34'      'Tomasevic'.

* show initial list (items with level 0 - parentless items)
LOOP AT ITEMS WHERE PARENT_ID = ''.
  MOVE-CORRESPONDING ITEMS TO ITEMS_SHOW.
  ITEMS_SHOW-SYMBOL = '+'.
  APPEND ITEMS_SHOW.
ENDLOOP.
PERFORM PRINT_TREE TABLES ITEMS_SHOW.

* at line-selection - when the node is opened/closed or item double-clk
AT LINE-SELECTION.
  READ TABLE ITEMS WITH KEY PARENT_ID = ITEMS_SHOW-ID. "see 'hide'
  IF SY-SUBRC = 0. "item has children - expand or collapse
    SY-LSIND = 0.
    PERFORM EXPAND_COLLAPSE USING ITEMS_SHOW-ID.
    PERFORM PRINT_TREE TABLES ITEMS_SHOW.
  ELSE.            "item has NO children - perform some action
    READ TABLE ITEMS WITH KEY ID = ITEMS_SHOW-ID.
    WRITE: 'Action performed on item "' NO-GAP, ITEMS-TEXT NO-GAP,
           '", id.', ITEMS-ID.
  ENDIF.

* form print_tree
FORM PRINT_TREE TABLES ITEMS STRUCTURE ITEMS.
  DATA: V_TABIX LIKE SY-TABIX,
        START_TABIX LIKE SY-TABIX,
        V_LEVEL LIKE SY-TFILL,
        V_OFFSET TYPE I,
        V_ID LIKE ITEMS-ID,
        V_PARENT_ID LIKE ITEMS-PARENT_ID,
        V_PARENT_ID_FOR_VLINE LIKE ITEMS-PARENT_ID,
        V_PREV_LEVEL TYPE I,
        V_ITEMS_COUNT LIKE SY-TFILL,
        V_VLINES_STRING(200).
  CHECK NOT ITEMS[] IS INITIAL.
  SORT ITEMS BY PARENT_ID ID.
  READ TABLE ITEMS INDEX 1.
  V_PARENT_ID = ITEMS-PARENT_ID.
  START_TABIX = 1.
  REFRESH TABIX_STACK.
  DO.
    LOOP AT ITEMS FROM START_TABIX.
      V_TABIX = START_TABIX = SY-TABIX."remember current index
      V_ID = ITEMS-ID.
      V_PARENT_ID_FOR_VLINE = ITEMS-PARENT_ID.
*     decrease level and exit loop if parent not the same as previous
      IF ITEMS-PARENT_ID NE V_PARENT_ID.
        PERFORM READ_FROM_STACK CHANGING START_TABIX. "level = NoOfRecs
        READ TABLE ITEMS INDEX START_TABIX.
        V_PARENT_ID = ITEMS-PARENT_ID.
        ADD 1 TO START_TABIX.   "next loop starts from parent index + 1
*        clear vline
        IF V_LEVEL > 1.
          V_OFFSET = 2 + ( V_LEVEL - 2 ) * 3.
          IF V_LEVEL = 1. V_OFFSET = 1. ENDIF.
          V_VLINES_STRING+V_OFFSET = ' '.
        ENDIF.
        EXIT.
      ENDIF.
      V_PARENT_ID = ITEMS-PARENT_ID.
*     write item
      FORMAT COLOR OFF.
      DESCRIBE TABLE TABIX_STACK LINES V_LEVEL."level is no of
StackRecs
      WRITE: / V_VLINES_STRING.
      V_OFFSET = V_LEVEL * 3.
      IF V_LEVEL NE 0.
        IF V_PREV_LEVEL < V_LEVEL.
          WRITE: AT V_OFFSET '|', / ''.
          WRITE: / V_VLINES_STRING.
        ENDIF.
        V_OFFSET = V_LEVEL * 3.
        WRITE AT V_OFFSET '|--'.
      ENDIF.
      V_OFFSET = V_OFFSET + 3.
      CASE ITEMS-SYMBOL.
        WHEN '+'.
          WRITE AT V_OFFSET SYM_PLUS_FOLDER AS SYMBOL
                COLOR 4 INTENSIFIED HOTSPOT.
        WHEN '-'.
          WRITE AT V_OFFSET SYM_MINUS_FOLDER AS SYMBOL
                COLOR 4 INTENSIFIED HOTSPOT.
        WHEN OTHERS. FORMAT COLOR 5.
      ENDCASE.
      WRITE: ITEMS-TEXT.
      V_PREV_LEVEL = V_LEVEL.
      HIDE: ITEMS-ID.
      ADD 1 TO V_ITEMS_COUNT.
      READ TABLE ITEMS WITH KEY PARENT_ID = ITEMS-ID.
*     increase level and exit loop if item has children
      IF SY-SUBRC = 0.
        START_TABIX = SY-TABIX.
        APPEND V_TABIX TO TABIX_STACK. "level is no of recs in stack
        V_PARENT_ID = ITEMS-PARENT_ID.
*        set vline
        V_TABIX = V_TABIX + 1.
        READ TABLE ITEMS INDEX V_TABIX.
        V_OFFSET = 2 + ( V_LEVEL - 1 ) * 3.
        IF V_LEVEL > 0.
          IF ITEMS-PARENT_ID = V_PARENT_ID_FOR_VLINE AND SY-SUBRC = 0.
            V_VLINES_STRING+V_OFFSET = '|'.
          ELSE.
            V_VLINES_STRING+V_OFFSET = ' '.
          ENDIF.
        ENDIF.
        EXIT.
      ENDIF.
*     at last - decrease level
      AT LAST.
*        clear vline
        IF V_LEVEL > 1.
          V_OFFSET = 2 + ( V_LEVEL - 2 ) * 3.
          IF V_LEVEL = 1. V_OFFSET = 1. ENDIF.
          V_VLINES_STRING+V_OFFSET = ' '.
        ENDIF.
        " next loop starts from parent index, not parent index + 1
        " because of different parents level will decrease anyway
        PERFORM READ_FROM_STACK CHANGING START_TABIX.
        APPEND START_TABIX TO TABIX_STACK. "must return index to stack
      ENDAT.
    ENDLOOP.
    DESCRIBE TABLE ITEMS.
    IF START_TABIX > SY-TFILL OR V_ITEMS_COUNT >= SY-TFILL.
      EXIT.
    ENDIF.
  ENDDO.
ENDFORM.

* form expand_collapse
FORM EXPAND_COLLAPSE USING VALUE(V_ID).
  DATA: V_NO_MORE_ORPHANS,
        ITEMS_TEMP LIKE ITEMS OCCURS 100 WITH HEADER LINE.
  DELETE ITEMS_SHOW WHERE PARENT_ID = V_ID. "try to collapse
  IF SY-SUBRC = 0.                     "succesfull first collapse
    DO.            "cascade collapse - delete 'orphans' that are left
      REFRESH ITEMS_TEMP.
      MOVE ITEMS_SHOW[] TO ITEMS_TEMP[].
      SORT ITEMS_TEMP BY ID.
      V_NO_MORE_ORPHANS = 'X'.
      LOOP AT ITEMS_SHOW WHERE PARENT_ID NE ''.
        READ TABLE ITEMS_TEMP WITH KEY ID = ITEMS_SHOW-PARENT_ID
                               BINARY SEARCH TRANSPORTING NO FIELDS.
        IF SY-SUBRC NE 0.              "no parent - it's an orphan
          CLEAR V_NO_MORE_ORPHANS.
          DELETE ITEMS_SHOW.
        ENDIF.
      ENDLOOP.
      IF V_NO_MORE_ORPHANS = 'X'. EXIT. ENDIF.
    ENDDO.
    ITEMS_SHOW-SYMBOL = '+'.
    MODIFY ITEMS_SHOW TRANSPORTING SYMBOL WHERE ID = V_ID.
  ELSE.                                "unsuccessfull collapse - expand
    ITEMS_SHOW-SYMBOL = '-'.
    MODIFY ITEMS_SHOW TRANSPORTING SYMBOL WHERE ID = V_ID.
    LOOP AT ITEMS WHERE PARENT_ID = V_ID.      "show children
      APPEND ITEMS TO ITEMS_SHOW.
    ENDLOOP.
    LOOP AT ITEMS_SHOW WHERE PARENT_ID = V_ID. "check grandchildren
      READ TABLE ITEMS WITH KEY PARENT_ID = ITEMS_SHOW-ID.
      IF SY-SUBRC = 0.
        ITEMS_SHOW-SYMBOL = '+'.
      ELSE.
        ITEMS_SHOW-SYMBOL = ''.
      ENDIF.
      MODIFY ITEMS_SHOW.
    ENDLOOP.
  ENDIF.
ENDFORM.

* form append_item
FORM APPEND_ITEM USING VALUE(ID) VALUE(PARENT_ID) VALUE(TEXT).
  ITEMS-ID = ID.
  ITEMS-PARENT_ID = PARENT_ID.
  ITEMS-TEXT = TEXT.
  APPEND ITEMS.
ENDFORM.

* form read_from_stack
FORM READ_FROM_STACK CHANGING TABIX LIKE SY-TABIX.
  DESCRIBE TABLE TABIX_STACK.
  CHECK SY-TFILL NE 0.
  READ TABLE TABIX_STACK INDEX SY-TFILL.
  TABIX = TABIX_STACK.
  DELETE TABIX_STACK INDEX SY-TFILL.
ENDFORM.

A demo program to create subscreen in your ABAP Program

2008-12-29T01:52:00.000-08:00

A demo program to create subscreen in your ABAP Program
*
* This report will display the user last login date and time.
*
* Subscreen selection 1 : User Name
* 2 : Last Login Date
* 3 : Class Belong To
*
* Written by : SAP Basis, ABAP Programming and Other IMG Stuff
* http://www.sap-img.com
*

REPORT ZSUBSCREEN.

TABLES: USR02,       "Logon data
        SSCRFIELDS.  "FIELDS ON SELECTION SCREENS
*---------------------------------------------------------------
* SUBSCREEN 1
*---------------------------------------------------------------
SELECTION-SCREEN BEGIN OF SCREEN 100 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-010.
   SELECT-OPTIONS: USERNAME FOR USR02-BNAME.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN END OF SCREEN 100.

*---------------------------------------------------------------
* SUBSCREEN 2
*---------------------------------------------------------------
SELECTION-SCREEN BEGIN OF SCREEN 200 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-020.
   SELECT-OPTIONS: LASTLOGI FOR USR02-TRDAT.
SELECTION-SCREEN END OF BLOCK B2.
SELECTION-SCREEN END OF SCREEN 200.

*---------------------------------------------------------------
* SUBSCREEN 3
*---------------------------------------------------------------
SELECTION-SCREEN BEGIN OF SCREEN 300 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME TITLE TEXT-030.
   SELECT-OPTIONS: CLASSTYP FOR USR02-CLASS.
SELECTION-SCREEN END OF BLOCK B3.
SELECTION-SCREEN END OF SCREEN 300.

* STANDARD SELECTION SCREEN FOR SCROLLING LEFT AND RIGHT
SELECTION-SCREEN: FUNCTION KEY 1,
                  FUNCTION KEY 2.

SELECTION-SCREEN: BEGIN OF TABBED BLOCK SUB FOR 15 LINES,
                  END OF BLOCK SUB.

START-OF-SELECTION.
    SELECT * FROM USR02 WHERE BNAME IN USERNAME
                          AND ERDAT IN LASTLOGI
                          AND CLASS IN CLASSTYP.
       WRITE: / 'User ', USR02-BNAME,
                'Last Login Date ', USR02-TRDAT,
                'Last Login Time ', USR02-LTIME,
                'CLASS ', USR02-CLASS.
    ENDSELECT.
END-OF-SELECTION.

INITIALIZATION.
* SCREEN ICON LEFT AND RIGHT
  SSCRFIELDS-FUNCTXT_01 = '@0D@'.
  SSCRFIELDS-FUNCTXT_02 = '@0E@'.
  SUB-PROG = SY-REPID.
  SUB-DYNNR = 100.

AT SELECTION-SCREEN.
  CASE SY-DYNNR.

    WHEN 100.
      IF SSCRFIELDS-UCOMM = 'FC01'.
        SUB-DYNNR = 300.
      ELSEIF SSCRFIELDS-UCOMM = 'FC02'.
        SUB-DYNNR = 200.
      ENDIF.

    WHEN 200.
      IF SSCRFIELDS-UCOMM = 'FC01'.
        SUB-DYNNR = 100.
      ELSEIF SSCRFIELDS-UCOMM = 'FC02'.
        SUB-DYNNR = 300.
      ENDIF.

    WHEN 300.
      IF SSCRFIELDS-UCOMM = 'FC01'.
        SUB-DYNNR = 200.
      ELSEIF SSCRFIELDS-UCOMM = 'FC02'.
        SUB-DYNNR = 100.
      ENDIF.
  ENDCASE.

TABStrips in ABAP

2008-12-29T01:51:00.000-08:00

 Different Selection Options separated by Tabstrips 1,2 and 3
*
* Written by : SAP Basis, ABAP Programming and Other IMG Stuff
*              http://www.sap-img.com
*
REPORT  ZTABSTRIPS  LINE-SIZE 120
        NO STANDARD PAGE HEADING.

TABLES: ekko, ekpo, eket, marc, t134h.

*---------------------------------------------------------------------*
*   Tab Strips 1
*---------------------------------------------------------------------*
SELECTION-SCREEN BEGIN OF SCREEN 101 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK vendor WITH FRAME TITLE text-t00.
SELECT-OPTIONS vendor FOR ekko-lifnr.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (10) text-m01.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN SKIP.
SELECT-OPTIONS vplant FOR ekko-reswk.
SELECTION-SCREEN END OF BLOCK vendor.
SELECTION-SCREEN END OF SCREEN 101.
*---------------------------------------------------------------------*
*   Tab Strips 2
*---------------------------------------------------------------------*
SELECTION-SCREEN BEGIN OF SCREEN 102 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK data1 WITH FRAME TITLE text-t02.
SELECT-OPTIONS: busarea FOR t134h-gsber,
                plant   FOR ekpo-werks,
                puorg   FOR ekko-ekorg.
SELECTION-SCREEN END OF BLOCK data1.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF BLOCK data2 WITH FRAME TITLE text-t03.
SELECT-OPTIONS  sched   FOR ekko-ebeln.
SELECT-OPTIONS  matl    FOR ekpo-matnr.
SELECTION-SCREEN END OF BLOCK data2.
SELECTION-SCREEN END OF SCREEN 102.
*---------------------------------------------------------------------*
*   Tab Strips 3
*---------------------------------------------------------------------*
SELECTION-SCREEN BEGIN OF SCREEN 103 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK rype WITH FRAME TITLE text-t04.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS del RADIOBUTTON GROUP one.
SELECTION-SCREEN COMMENT 4(35) text-c05 FOR FIELD del.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS fix RADIOBUTTON GROUP one.
SELECTION-SCREEN COMMENT 4(35) text-c06 FOR FIELD fix.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK rype.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF BLOCK interval WITH FRAME TITLE text-t05.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS mon RADIOBUTTON GROUP two.
SELECTION-SCREEN COMMENT 4(15) text-c01 FOR FIELD mon.
PARAMETERS evalmon TYPE spbup.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS wek RADIOBUTTON GROUP two.
SELECTION-SCREEN COMMENT 4(15) text-c02 FOR FIELD wek.
PARAMETERS evalweek TYPE sptag.
SELECTION-SCREEN COMMENT 35(30) text-i01.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK interval.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF BLOCK type WITH FRAME TITLE text-t01.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS ext RADIOBUTTON GROUP thr.
SELECTION-SCREEN COMMENT 4(15) text-c08 FOR FIELD int.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS int RADIOBUTTON GROUP thr.
SELECTION-SCREEN COMMENT 4(15) text-c07 FOR FIELD ext.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK type.
SELECTION-SCREEN BEGIN OF BLOCK pre WITH FRAME TITLE text-t06.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS vn RADIOBUTTON GROUP slv.
SELECTION-SCREEN COMMENT 4(15) text-c09 FOR FIELD vn.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS bp RADIOBUTTON GROUP slv.
SELECTION-SCREEN COMMENT 4(17) text-c10 FOR FIELD bp.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK pre.
SELECTION-SCREEN END OF SCREEN 103.

SELECTION-SCREEN BEGIN OF TABBED BLOCK uno FOR 20 LINES.
SELECTION-SCREEN TAB (15) name1 USER-COMMAND ucomm1
DEFAULT SCREEN 101.
SELECTION-SCREEN TAB (17) name2 USER-COMMAND ucomm2
DEFAULT SCREEN 102.
SELECTION-SCREEN TAB (23) name3 USER-COMMAND ucomm3
DEFAULT SCREEN 103.
SELECTION-SCREEN END OF BLOCK uno.

INITIALIZATION.
  name1 = text-n01.
  name2 = text-n02.
  name3 = text-n03.

Example Code For Drill Down Report

2008-12-29T01:48:00.000-08:00

REPORT  zmm_rept_purchorderkkb01 LINE-SIZE 80
                                 LINE-COUNT 65(3)
                                 MESSAGE-ID z_msg_class
                                 NO STANDARD PAGE HEADING.

*------------------DECLARING THE STANDARD TABLES---------------------*
TABLES : ekko, "PURCHASE ORDER : HEADER
         ekpo. "PURCHASE ORDER : ITEM

*------------------DECLARING THE INTERNAL TABLE----------------------*
DATA  : BEGIN OF it_ekko OCCURS 2,
          ebeln LIKE ekko-ebeln, "PURCHASE ORDER NUMBER
          bukrs LIKE ekko-bukrs, "COMPANY CODE
          bsart LIKE ekko-bsart, "PURCHASING DOCUMENT TYPE
          lifnr LIKE ekko-lifnr, "VENDOR
          spras LIKE ekko-spras, "LANGUAGE KEY
          zterm LIKE ekko-zterm, "PAYMENT TERMS KEY
        end of it_ekko.

DATA  : BEGIN OF it_ekpo OCCURS 2,
          ebeln LIKE ekpo-ebeln, "PURCHASE ORDER NUMBER
          ebelp LIKE ekpo-ebelp, "PURCHASE ORDER NUMBER
          werks LIKE ekpo-werks, "PLANT
          matnr LIKE ekpo-matnr, "MATERIAL NUMBER
          matkl LIKE ekpo-matkl, "MATERIAL GROUP
        END OF it_ekpo.

DATA: it_ebeln LIKE ekko-ebeln OCCURS 0 WITH HEADER LINE.

*DATA: it_ebeln_high LIKE ekko-ebeln OCCURS 0 WITH HEADER LINE.

DATA: p_ebeln       TYPE i.

*------------------Declaring the selection screen--------------------*

SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001.

SELECT-OPTIONS : s_ebeln FOR ekko-ebeln.

PARAMETER      : p_limit TYPE i.

SELECTION-SCREEN END OF BLOCK blk1.


*INCLUDE z_incl_purorderkkb01_sub_f01.


*--------------------------------------------------------------------*
*  Validation for  number of records to be printed                   *
*--------------------------------------------------------------------*

*AT SELECTION-SCREEN ON p_limit.
*  IF p_limit IS INITIAL.
*    MESSAGE e011.
*  ENDIF.


*  IF p_limit GT sy-linct.
*    MESSAGE e010.
*  ENDIF.


*----------------------------------------------------------------------*
*        Search help for purchase document number (s_ebeln-low)        *
*----------------------------------------------------------------------*

AT SELECTION-SCREEN ON VALUE-REQUEST FOR s_ebeln-low.
  CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input  = s_ebeln-low
    IMPORTING
      output = s_ebeln-low.

  perform form_search_help.

  IF sy-subrc <> 0.
    CASE sy-subrc.
      WHEN 2.
        LEAVE TO SCREEN 1000.
    ENDCASE.
  ELSE.
    LOOP AT it_ebeln.
      IF sy-tabix = p_ebeln.
        s_ebeln-low = it_ebeln.
        EXIT.
      ENDIF.
    ENDLOOP.
  ENDIF.

*----------------------------------------------------------------------*
*        Search help for purchase document number (s_ebeln-high)       *
*----------------------------------------------------------------------*

AT SELECTION-SCREEN ON VALUE-REQUEST FOR s_ebeln-high.
  CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input  = s_ebeln-high
    IMPORTING
      output = s_ebeln-high.

  perform form_search_help.

  IF sy-subrc <> 0.
    CASE sy-subrc.
      WHEN 2.
        LEAVE TO SCREEN 1000.
    ENDCASE.
  ELSE.
    LOOP AT it_ebeln.
      IF sy-tabix = p_ebeln.
        s_ebeln-high = it_ebeln.
        EXIT.
      ENDIF.
    ENDLOOP.
  ENDIF.

*----------------------------------------------------------------------*
*                   Start-of-selection event                           *
*----------------------------------------------------------------------*

START-OF-SELECTION.

*----------------------To attach a user interface----------------------*
SET PF-STATUS '0010'.

*---------To fetch the data for the basic list-------------------------*
    SELECT ebeln                   "PURCHASE ORDER NUMBER
           bukrs                   "COMPANY CODE
           bsart                   "PURCHASING DOCUMENT TYPE
           lifnr                   "VENDOR
           spras                   "LANGUAGE KEY
           zterm                   "PAYMENT TERMS KEY
     up to p_limit rows
     into table it_ekko from ekko
     where ebeln in s_ebeln.

     REFRESH it_ekpo.

*---------To fetch the data for the secondary list-----------------------*

if it_ekpo is initial.

    SELECT ebeln "PURCHASE ORDER NUMBER
           ebelp "PURCHASING DOCUMENT TYPE
           werks "PLANT
           matnr "MATERIAL NUMBER
           matkl "MATERIAL GROUP
    FROM ekpo  INTO TABLE it_ekpo for all entries in it_ekko
    WHERE ebeln EQ it_ekko-ebeln.

endif.

*----------------------------------------------------------------------*
*                   End-of-selection event                             *
*----------------------------------------------------------------------*

END-OF-SELECTION.


*---------To display the data for the basic list-----------------------*
   format color 4 intensified off.
  LOOP AT it_ekko.
    WRITE :/ sy-vline, it_ekko-ebeln UNDER text-002, 18 sy-vline,
                                                    "PURCHASE ORDER NUMBER
                       it_ekko-bukrs UNDER text-003, 27 sy-vline,
                                                    "COMPANY CODE
                       it_ekko-bsart UNDER text-004, 38 sy-vline,
                                                    "PURCHASING DOCUMENT TYPE
                       it_ekko-lifnr UNDER text-005, 50 sy-vline,
                                                    "VENDOR
                       it_ekko-spras UNDER text-006, 62 sy-vline,
                                                    "LANGUAGE KEY
                       it_ekko-zterm UNDER text-007, 80 sy-vline.
                                                    "PAYMENT TERMS KEY

  hide : it_ekko-ebeln.
  ENDLOOP.
  WRITE :/ sy-uline(80).

*----------------------------------------------------------------------*
*                To generate the detailed lists                        *
*----------------------------------------------------------------------*

AT LINE-SELECTION.
  CASE sy-lsind.
    WHEN 1.
      SET PF-STATUS '0011'.

*---------To display the data for the secondary list-----------------------*
WINDOW STARTING AT 10 10
       ENDING   AT 90 30.
    format color 5 intensified off.
  LOOP AT it_ekpo where ebeln = it_ekko-ebeln .
    WRITE :/ sy-vline, it_ekpo-ebeln UNDER text-002, 15 sy-vline,
                                                     "PURCHASE ORDER NUMBER
                       it_ekpo-ebelp UNDER text-008, 30 sy-vline,
                                                     "PO ITEM NUMBER
                       it_ekpo-werks UNDER text-009, 45 sy-vline,
                                                     "PLANT
                       it_ekpo-matnr UNDER text-010, 60 sy-vline,
                                                     "MATERIAL NUMBER
                       it_ekpo-matkl UNDER text-011, 80 sy-vline.
                                                     "MATERIAL GROUP
  ENDLOOP.

  WRITE :/ sy-uline(80).

  ENDCASE.

  CASE sy-ucomm.
    WHEN 'EXIT' OR 'CANC' OR 'BACK'.
       LEAVE TO SCREEN 0.
  ENDCASE.

*----------------------------------------------------------------------*
*                    At user-command event                             *
*----------------------------------------------------------------------*

AT USER-COMMAND.
  CASE sy-ucomm.
    WHEN 'SELE' OR 'LIST1'.
      IF sy-lsind = 1.
      SET PF-STATUS '0011'.

*---------To display the data for the secondary list-----------------------*

WINDOW STARTING AT 10 10
       ENDING   AT 90 30.
       format color 5 intensified off.

  LOOP AT it_ekpo where ebeln = it_ekko-ebeln .
    WRITE :/ sy-vline, it_ekpo-ebeln UNDER text-002, 15 sy-vline, "PURCHASE ORDER NUMBER
                       it_ekpo-ebelp UNDER text-008, 30 sy-vline, "PO ITEM NUMBER
                       it_ekpo-werks UNDER text-009, 45 sy-vline, "PLANT
                       it_ekpo-matnr UNDER text-010, 60 sy-vline, "MATERIAL NUMBER
                       it_ekpo-matkl UNDER text-011, 80 sy-vline. "MATERIAL GROUP

  ENDLOOP.

  WRITE :/ sy-uline(80).
  endif.

  ENDCASE.

  CASE sy-ucomm.
    WHEN 'EXIT' OR 'CANC' OR 'BACK'.
       LEAVE TO SCREEN 0.

  ENDCASE.

*----------------------------------------------------------------------*
*                    Top-of-page for basic list                        *
*----------------------------------------------------------------------*

TOP-OF-PAGE.

 format color 3 intensified off.

  WRITE :/ sy-uline(80).
  WRITE :/    sy-vline,
           03 sy-repid,
           60 text-015,
              sy-uname,
           80 sy-vline.
  WRITE :/ sy-vline, 03 sy-datum,
           35 text-012,
           60 text-014,
              sy-pagno,
           80 sy-vline.
  WRITE :/ sy-uline(80).
  WRITE :/ sy-vline, text-002, 18 sy-vline, "PURCHASE ORDER NUMBER
                     text-003, 27 sy-vline, "COMPANY CODE
                     text-004, 38 sy-vline, "PURCHASING DOCUMENT TYPE
                     text-005, 50 sy-vline, "VENDOR
                     text-006, 62 sy-vline, "LANGUAGE KEY
                     text-007, 80 sy-vline. "PAYMENT TERMS KEY
  WRITE :/ sy-uline(80).

*----------------------------------------------------------------------*
*              Top-of-page for secondary list                          *
*----------------------------------------------------------------------*

TOP-OF-PAGE DURING LINE-SELECTION.
format color 2 intensified off.
WINDOW STARTING AT 10 10
       ENDING   AT 90 30.
  WRITE :/ sy-uline(80).
  WRITE :/   sy-vline,
          03 sy-repid,
          60 text-015,
             sy-uname,
          80 sy-vline.

  WRITE :/   sy-vline,
          03 sy-datum,
          35 text-013,
          60 text-014,
             sy-pagno,
          80 sy-vline.

  WRITE :/ sy-uline(80).

  WRITE :/ sy-vline, text-014, 15 sy-vline, "PURCHASE ORDER NUMBER
                     text-008, 30 sy-vline, "PO ITEM NUMBER
                     text-009, 45 sy-vline, "PLANT
                     text-010, 60 sy-vline, "MATERIAL NUMBER
                     text-011, 80 sy-vline. "MATERIAL GROUP

  WRITE :/ sy-uline(80).

*----------------------------------------------------------------------*
*                    End-of-page event                                 *
*----------------------------------------------------------------------*

END-OF-PAGE.
  WRITE :/    sy-vline,
           03 text-016,
              p_limit,
           60 text-014,
              sy-pagno,
           80 sy-vline.
  write:/ sy-uline(80).

INCLUDE Z_INCLUDE_PURCHORDERKKB01.
form form_search_help .

REFRESH it_ebeln.
  CLEAR it_ebeln.
  CLEAR P_ebeln.

  SELECT ebeln FROM ekko INTO TABLE it_ebeln.

  CALL FUNCTION 'POPUP_WITH_TABLE_DISPLAY'
    EXPORTING
      endpos_col   = 21
      endpos_row   = 35
      startpos_col = 12
      startpos_row = 1
      titletext    = text-012

    IMPORTING
      choise       = P_ebeln

    TABLES
      valuetab     = it_ebeln

    EXCEPTIONS
      break_off    = 1
      OTHERS       = 2.

Tips By : Kavuri

List Box in ABAP Report

2008-12-29T01:46:00.000-08:00

 List Box in ABAP Report
*
* Written by : SAP Basis, ABAP Programming and Other IMG Stuff
*              http://www.sap-img.com
*
REPORT ZLIST.

TYPE-POOLS: VRM.

DATA: NAME  TYPE VRM_ID,
      LIST  TYPE VRM_VALUES,
      VALUE LIKE LINE OF LIST.

PARAMETERS: PS_PARM(10) AS LISTBOX VISIBLE LENGTH 10.

AT SELECTION-SCREEN OUTPUT.

NAME = 'PS_PARM'.
VALUE-KEY = '1'.

VALUE-TEXT = 'LINE 1'.
APPEND VALUE TO LIST. VALUE-KEY = '2'.

VALUE-TEXT = 'LINE 2'.
APPEND VALUE TO LIST.

CALL FUNCTION 'VRM_SET_VALUES' EXPORTING ID = NAME VALUES = LIST.

START-OF-SELECTION.
WRITE: / 'PARAMETER:', PS_PARM.

ABAP Enhancement

2008-12-29T01:43:00.000-08:00

General - Reporting Tree in ABAP

 An ABAP reporting tree program that allows the user to press enter or double click on
* any line. The report is updated with new internal table data and re-written. The cursor
* and paging returns to the exact same line the user was on, even though the report was
* re-written from the internal table. Input fields are filled with data based on ENTER of
* DOUBLE CLICK. [+] and [-] is displayed on each line and changes if user selects to
* expand/collapse.
*
* Create a gui status (8000) with Functions Keys
*                                 ENTER        = ENTE
*                                 BACK         = BACK
*                                 EXIT         = %EX
*                                 CANCEL       = RW
*                                 PICK         = F2
*                                 EXPAND ALL   = EXPA
*                                 COLLAPSE ALL = COLA
*
* Written by : SAP Basis, ABAP Programming and Other IMG Stuff
*              http://www.sap-img.com
*
REPORT ZTREE NO STANDARD PAGE HEADING
             LINE-COUNT 65
             LINE-SIZE 80.

DATA: BEGIN OF IT_DATA OCCURS 0,
        EXP(1) TYPE C,
        WERKS LIKE T001W-WERKS,
        MATNR LIKE MARA-MATNR,
        VALUE1(13) TYPE C,
        VALUE2(13) TYPE C,
      END OF IT_DATA.

DATA: W_MATNR LIKE MARA-MATNR,
      W_COUNT TYPE I,
      G_FIELD(40) TYPE C.

DATA: BEGIN OF PAGE,
        SCRLLINE LIKE SYST-LILLI,      "scroll line to top of screen
        CURSLINE LIKE SYST-LILLI,      "line to put cursor on
        HDRLINES TYPE I,               "lines in header + 1
        TWOHDRS TYPE I,                "two headers on screen
        CPOSTOP TYPE I,                "position of cursor from top
        CPOSBOT TYPE I,                "position of cursor from bottom
        CPOSIT TYPE I,                 "position on the screen
        PAGNO TYPE I,                  "pageno of line
        PGELINES TYPE I,               "lines used so far
      END OF PAGE.

START-OF-SELECTION.
  PERFORM BUILD_IT_DATA.

END-OF-SELECTION.
  PERFORM WRITE_REPORT.

TOP-OF-PAGE.
  PERFORM TOP_OF_PAGE.

TOP-OF-PAGE DURING LINE-SELECTION.
  PERFORM TOP_OF_PAGE.

AT LINE-SELECTION.
  G_FIELD = SPACE.
  GET CURSOR FIELD G_FIELD.
  PERFORM LINE_SELECTION.

AT USER-COMMAND.
  G_FIELD = SPACE.
  GET CURSOR FIELD G_FIELD.
  PERFORM USER_COMMAND.

*---------------------------------------------------------------------*
*       FORM BUILD_IT_DATA                                            *
*---------------------------------------------------------------------*
FORM BUILD_IT_DATA.
  IT_DATA-WERKS = '0000'.
  WHILE IT_DATA-WERKS < '0100'.
    ADD '10' TO IT_DATA-WERKS.
    W_MATNR = 0.
    WHILE W_MATNR < 10.
      ADD 1 TO W_MATNR.
      IT_DATA-EXP = '+'.
      WRITE W_MATNR TO IT_DATA-MATNR.
      IF IT_DATA-WERKS = 10 AND W_MATNR = 1.
            WRITE 'ZTEST2' TO IT_DATA-VALUE1.
            WRITE 'Testing program 2' TO IT_DATA-VALUE2.
      ELSE.
            CLEAR: IT_DATA-VALUE1, IT_DATA-VALUE2.
      ENDIF.
      APPEND IT_DATA.
    ENDWHILE.
  ENDWHILE.
ENDFORM.
*---------------------------------------------------------------------*
*       FORM WRITE_REPORT                                             *
*---------------------------------------------------------------------*
FORM WRITE_REPORT.
  SET PF-STATUS '8000'.
  SYST-LSIND = '0'.
  LOOP AT IT_DATA.
    AT NEW WERKS.
      FORMAT COLOR COL_HEADING INTENSIFIED OFF.
      WRITE: /1 SYST-VLINE NO-GAP,
                '[' NO-GAP,
                IT_DATA-EXP NO-GAP HOTSPOT ON,
                ']'.
      FORMAT COLOR COL_NORMAL INTENSIFIED ON.
      WRITE:     IT_DATA-WERKS,
              AT SYST-LINSZ SYST-VLINE.
      PAGE-PAGNO = SYST-PAGNO.
      HIDE: IT_DATA-WERKS, PAGE-PAGNO.
    ENDAT.
    IF IT_DATA-EXP = '-'.
      FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
      WRITE: /1 SYST-VLINE,
              8 IT_DATA-MATNR,
                IT_DATA-VALUE1 INPUT ON,
                IT_DATA-VALUE2 INPUT ON,
             AT SYST-LINSZ SYST-VLINE.
      HIDE: IT_DATA, PAGE-PAGNO.
    ENDIF.
  ENDLOOP.
  ULINE.
ENDFORM.
*---------------------------------------------------------------------*
*       FORM USER_COMMAND                                             *
*---------------------------------------------------------------------*
FORM USER_COMMAND.
  PERFORM SET_SCROLL_LINE.
  CASE SY-UCOMM.
    WHEN 'ENTE'.
      READ TABLE IT_DATA WITH KEY WERKS = IT_DATA-WERKS
                                  MATNR = IT_DATA-MATNR.
      IF SYST-SUBRC = 0.
        CASE G_FIELD.
          WHEN 'IT_DATA-VALUE1'.
            IF IT_DATA-VALUE1 <> SPACE.
               SUBMIT (IT_DATA-VALUE1) VIA SELECTION-SCREEN AND RETURN.
            ELSE.
               IT_DATA-VALUE1 = 'Enter 1 Press'(001).
            ENDIF.
          WHEN 'IT_DATA-VALUE2'.
            IT_DATA-VALUE2 = 'Enter 2 Press'(001).
        ENDCASE.
        MODIFY IT_DATA INDEX SYST-TABIX.
      ENDIF.
      PERFORM WRITE_REPORT.
      PERFORM POSITION_LIST.
      CASE G_FIELD.
        WHEN 'IT_DATA-EXP'.
          ADD 1 TO PAGE-CURSLINE.
          SET CURSOR FIELD 'IT_DATA-VALUE1' LINE PAGE-CURSLINE.
        WHEN 'IT_DATA-VALUE1'.
          SET CURSOR FIELD 'IT_DATA-VALUE1' LINE PAGE-CURSLINE.
        WHEN 'IT_DATA-VALUE2'.
          SET CURSOR FIELD 'IT_DATA-VALUE2' LINE PAGE-CURSLINE.
      ENDCASE.
    WHEN 'EXPA'.
      PERFORM SET_EXPAND USING '-'.
      PERFORM WRITE_REPORT.
    WHEN 'COLA'.
      PERFORM SET_EXPAND USING '+'.
      PERFORM WRITE_REPORT.
  ENDCASE.
ENDFORM.
*---------------------------------------------------------------------*
*       FORM SET_EXPAND                                               *
*---------------------------------------------------------------------*
FORM SET_EXPAND USING W_EXP.
  LOOP AT IT_DATA.
    IT_DATA-EXP = W_EXP.
    MODIFY IT_DATA INDEX SYST-TABIX.
  ENDLOOP.
ENDFORM.
*---------------------------------------------------------------------*
*       FORM LINE_SELECTION                                           *
*---------------------------------------------------------------------*
FORM LINE_SELECTION.
  PERFORM SET_SCROLL_LINE.
  READ TABLE IT_DATA WITH KEY WERKS = IT_DATA-WERKS
                              MATNR = IT_DATA-MATNR.
  CASE G_FIELD.
    WHEN 'IT_DATA-EXP'.
      LOOP AT IT_DATA WHERE WERKS = IT_DATA-WERKS.
        IF IT_DATA-EXP = '-'.
          IT_DATA-EXP = '+'.
        ELSE.
          IT_DATA-EXP = '-'.
        ENDIF.
        MODIFY IT_DATA INDEX SYST-TABIX.
      ENDLOOP.
    WHEN 'IT_DATA-VALUE1'.
      IT_DATA-VALUE1 = 'Double Click'(004).
      MODIFY IT_DATA INDEX SYST-TABIX.
    WHEN 'IT_DATA-VALUE2'.
      IT_DATA-VALUE2 = 'Double Click'(004).
      MODIFY IT_DATA INDEX SYST-TABIX.
  ENDCASE.
  PERFORM WRITE_REPORT.
  PERFORM POSITION_LIST.
  CASE G_FIELD.
    WHEN 'IT_DATA-EXP'.
      ADD 1 TO PAGE-CURSLINE.
      SET CURSOR FIELD 'IT_DATA-VALUE1' LINE PAGE-CURSLINE.
    WHEN 'IT_DATA-VALUE1'.
      SET CURSOR FIELD 'IT_DATA-VALUE1' LINE PAGE-CURSLINE.
    WHEN 'IT_DATA-VALUE2'.
      SET CURSOR FIELD 'IT_DATA-VALUE2' LINE PAGE-CURSLINE.
  ENDCASE.
ENDFORM.
*---------------------------------------------------------------------*
*       FORM SET_SCROLL_LINE                                          *
* determine the correct line to scroll the re-written report to, so   *
* that the user is returned to the same spot on the screen            *
* if user is mid way between pages, ie two headers are visable on the *
* screen, check if they are on the secondary page and adjust the      *
* scroll variable accordingly so as not to jump up lines because the  *
* scroll variable will be out by the number of lines in the extra hdr *
*---------------------------------------------------------------------*
FORM SET_SCROLL_LINE.
  PAGE-CURSLINE = SYST-LILLI.
  PAGE-SCRLLINE = SYST-LILLI - ( SYST-CUROW - PAGE-HDRLINES ).
  PAGE-PGELINES = ( PAGE-PAGNO - 1 ) * SYST-LINCT.
  PAGE-CPOSTOP = ( PAGE-SCRLLINE + SYST-CUROW ) - PAGE-PGELINES.
  PAGE-CPOSBOT = ( PAGE-SCRLLINE - SYST-CUROW ) - PAGE-PGELINES.
  PAGE-CPOSIT = PAGE-CPOSTOP + PAGE-CPOSBOT.
  PAGE-TWOHDRS = PAGE-HDRLINES * 2.
  IF PAGE-CPOSIT LT PAGE-TWOHDRS.
    PAGE-SCRLLINE = PAGE-SCRLLINE + 1.
  ENDIF.
ENDFORM.
*---------------------------------------------------------------------*
*       FORM POSITION_LIST                                            *
*---------------------------------------------------------------------*
FORM POSITION_LIST.
  CALL FUNCTION 'LIST_SCROLL_LINE_TOPMOST'
       EXPORTING
            LIST_INDEX = 1
            LIST_LINE  = PAGE-SCRLLINE
       EXCEPTIONS
            OTHERS     = 1.
  CHECK SYST-SUBRC = 0.
ENDFORM.
*---------------------------------------------------------------------*
*       FORM TOP_OF_PAGE                                              *
*---------------------------------------------------------------------*
FORM TOP_OF_PAGE.
* set page-hdrlines = lines in header + 1 system generated blank line
  PAGE-HDRLINES = 5.
  ULINE.
  WRITE : /1 SYST-VLINE, 'Header'(002), AT SYST-LINSZ SYST-VLINE.
  WRITE : /1 SYST-VLINE, 'Lines'(003), AT SYST-LINSZ SYST-VLINE.
  ULINE.
ENDFORM.

Internal table in ABAP

2008-12-29T01:38:00.000-08:00

*An internal table is a run time instance. It get created when program starts execution.
*It get destroyed when program terminates. it has two different parts. HeaderLine(optional) & Body(Compulsory).
*Any value that comes to or goes from interanal table , that travels through headerline.\

*A related program is .

*declaration.
data: begin of inernaltable occurs 0,
x type c,
y type i,
end of itab.

*initializing headerline
internaltable-x = 'd'.
internaltable-y = 34.

*storing value into internal table

appene internaltable .
appene internaltable .
appene internaltable .

*reading internal table
loop at itab .
write: / internaltable-x, internaltable-y. "writes to output list
endloop.

ABAP Tips by : Abdul Sayeed
Email : sayeed_mail2005@yahoo.com

Fields of Internal Tables

SY-TABIX

Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.

APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.

COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.

LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.

READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.

SEARCH FOR sets SY-TABIX to the index of the table line in which the search string is found.

SY-TFILL

After the statements DESCRIBE TABLE, LOOP AT, and READ TABLE, SY-TFILL contains the number of lines in the relevant internal table.

SY-TLENG

After the statements DESCRIBE TABLE, LOOP AT, and READ TABLE, SY-TLENG contains the length of the lines in the relevant internal table.

SY-TOCCU

After the statements DESCRIBE TABLE, LOOP AT, and READ TABLE, SY-TLENG contains the initial amount of memory allocated to the relevant internal table.

Fast Links:
Get help for your ABAP problems
Do you have a ABAP Question?

SAP Books
SAP Certification, Functional, Basis Administration and ABAP Programming Reference Books

ABAP Tips
ABAP Forum for Discussion and Samples Program Codes for Abapers

Background Processing System Fields

2008-12-29T01:35:00.000-08:00

SY-BATCH

X if the ABAP program is running in the background, otherwise space

Batch Input

SY-BINPT

X while a batch input session is running and when an ABAP program is called using
CALL TRANSACTION USING, otherwise space.

OPTIONS FROM in the CALL TRANSACTION USING statement can set SY-BINPT to space either for
the entire duration of the program, or at the end of the BDC data.

SY-BINPT is always space during a CATT procedure

System Fields for Current Date and Time

2008-12-29T01:34:00.000-08:00

The following system fields are always set automatically.

The GET TIME statement synchronizes the time on the application server with the time on the database server and writes it to the field SY-UZEIT. SY-DATUM and the system fields for the local timezone (SY-TIMLO, SY-DATLO, and SY-ZONLO) are also reset.

SY-DATLO

User’s local date, for example 19981129, 19990628, …

SY-DATUM

Current application server date, for example 19981130, 19990627, …

SY-DAYST

X during summertime, otherwise space.

SY-FDAYW

Factory calendar day of the week: Monday = 1 … Friday = 5.

SY-TIMLO

User’s local time, for example 154353, 225312, …

SY-TZONE

Time difference in seconds between local time and Greenwich Mean Time (UTC), for example,
360, 10800.

SY-UZEIT

Current application server time. for example 164353, 215312, …

SY-ZONLO

User’s time zone, for example, EST, UTC, …

ABAP Forum for Discussion and Samples Program Codes for Abapers

2008-12-29T01:12:00.000-08:00

There are many Free ABAP Programming Goodies Stuff with examples and samples codes listed here. It also contains many Questions and Answers that Abapers frequently asked. ABAP is the official language used by SAP to write its application modules. If you have any ABAP questions, please feel free to raise your ABAP queries in the ABAP forum.

sapabaptutorials

2008-12-29T01:10:00.000-08:00

sapabaptutorials