Sunday 30 October 2011

Step by step LSMW Guide

LSMW to Update Customer Master Records with Transaction Recording
  
Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as CUST_REC as shown in Figure 1.


Figure 1  Conversion Task with Project, Subproject and Object

The main screen of LSMW provides wizard-like step-by-step tasks, as shown in Figure 2. To complete your data conversion, you need to execute these steps in sequence. Once a step is executed, the cursor is automatically positioned to the next step.

Note that these steps may look different depending upon your Personal menu settings. You could make step numbers visible by ‘Numbers on’ icon or hidden by ‘Numbers off’ icon. You can execute a step by double-clicking on the row. Toggle icon ‘Doubleclick=Display’ or ‘Doubleclick=Edit’, makes the step in ‘display’ mode or ‘change’ mode.


Figure 2 LSMW Wizard – initial screen


Step 1: Maintain Object attributes
In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.


Figure 3  Object type ‘Transaction Recording’

The system calls the transaction code XD02 and prompts you to complete the Change
Customer transaction, as shown in Figure 4. Enter the key customer information (I entered customer number 1000, sales organization 1000, distribution channel 01, and division 00) and choose ‘Sales’ view within ‘Sales area data’. Make changes to these three fields (I entered, sales office 1010, sales group 110, and customer group 01) and save the transaction.


Figure 4  Transaction recording for Transaction Code ‘XD02’

Once the transaction is completed, R/3 records the flow of screens and fields and saves the information, as shown in Figure 5.




Figure 5  Transaction recording overview

Note that the fields are populated with default values. The values you entered when you recorded the transaction are set by default.

Note that if you have more fields in the recording than needed, you can remove them by clicking ‘Remove Screen field’ icon. 

Observe that the transaction-recording process stores field names in a technical format. By pressing the F1 key on individual screen fields and then pressing the F9 key, the system displays technical names. You then can replace the technical names with descriptive names. Double-click on the field RF02D-KUNNR and enter the name as KUNNR and the description as Customer Account Number and remove the default value. (See Figure 6.)


Figure 6  Field attributes

Similarly, double-click on all other fields with default values and make appropriate changes. Once you have made changes, the recording overview screen looks like what you see in Figure 7.


Figure 7  Transaction Recording Overview – with screen field attributes

Save your changes. When you go back to the initial screen, you will see that the initial screen steps have changed. Since you want to import data via the BDC method, the Direct Input and IDoc-related steps are hidden, as they are not relevant.


Step 2. Maintain Source Structures

Give a name and a description to the source structure (Figure 8).

Figure 8  Source Structure


Step 3. Maintain Source Fields
In this step, you need to list what fields are present in the source structure. The easiest way is to click on ‘Table Maintenance’ icon to enter Fieldname, Type and Length for each fieldas shown in Figure 9 


Figure 9  Source fields of source Structure

Note that your input file will have four fields as key fields and you need to update three fields in the system.

Step 4: Maintain Structure Relations

Execute a step to ‘Maintain Structure Relations’. (See Figure 10.) Since, there is only one Source and Target Structure, the relationship is defaulted automatically.


Figure 10  Structure Relation

Step 5: Maintain field mapping and conversion rules

Field RF02D-D0310 represents that you chose ‘Sales view’ for the customer Master screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of ‘X’.

If your source file already has the field value, you choose rule ‘Source Field’.

Keep cursor on field ‘KUNNR’ and click on ‘Assign Source field’ icon to choose source field CUSTOMER from structure XD02S as shown in Figure 11.


Figure 11  Assign source fields

Similarly, assign ‘Source Field’ rules to the remaining fields.

Once all the fields are mapped, you should have an overview screen as shown in Figure 12.



























Figure 12  Field mapping and Conversion rules overview


Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case, that step is not required.


Step 7: Specify files
In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt. (See Figure 13.)






























Figure 13  File attributes

Create an Excel file (Figure 14) with your data and save it as a Tab-delimited text file on your local drive (C:\) and name it XD02.txt.


Figure 14   Source data in Excel file (saved as Tab delimited file)


Step 8: Assign files
Execute step ‘Assign Files’ (Figure 15) and the system automatically defaults the filename to the source structure.


Figure 15 Assign file to Source Structure


Step 9: Read data
In this step, LSMW reads the data (Figure 16) from the source file (from your PC’s local drive). You have the option to read only selected rows and convert data values to Internal format.


Figure 16  Read Data


Step 10: Display read data
This step (Figure 17) is optional. If required, you can review the field contents for the rows of data read.

Figure 17  Display Read Data

Step 11: Convert data
This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined, source fields are mapped to target fields.

Step 12: Display Converted data
Again this is an optional step to view how the source data is converted to internal SAP format (Figure 18).


Figure 18  Display Converted Data


Step 13: Create batch input session
Once the source data is converted in an internal format, you can create a batch session to process updates (Figure 19).


Figure 19  Create Batch Input Session


Step 14: Run Batch Input Session
You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in the system. You can confirm this by viewing the customer master records (XD03).


Note! Browsing thru these 14 steps, you may get a feeling that this is a very lengthy and time-consuming activity. However, for the purposes of demonstration, I have made it detailed. Although it looks lengthy, actually it takes hardly few hours from start-to-finish! After playing around with few simple LSMW scripts, you will find it so easy to change and create more complex ones.

Sunday 16 October 2011

SAP PM Configuration Guide

Step by step SAP PM Configuration Guide

Click here to view

Please follow Blog & Comment....:-)


<a href="http://www.blogcatalog.com">BlogCatalog</a>

SAP SD Configuration Guide

Step by step SAP SD Configuration Guide

Click here to view

The xenophobia ironed a pancake

Friday 7 October 2011

SAP R/3 Programming Tips


These are powerful ABAP/4 functions are very interesting and can bring some advantages. Improve your home development easily. They belong to standard objects and should never be changed.
  • Bp_event_raise

  • Trigger an event from ABAP/4 program.
     
  • Bp_joblog_read

  • Fetch job log executions filling the structure TBTC5.
     
  • G_set_get_all_values

  • Fetch values from a set filling the structure RGSB4.
     
  • Popup_to_confirm_loss_of_data

  • Create a dialog box in which you make a question whether the user wishes to perform a processing step with loss of data.
     
  • Popup_to_confirm_step

  • Create a dialog box in which you make a question whether the user wishes to perform the step.
     
  • Popup_to_confirm_with_message

  • Create a dialog box in which you inform the user about a specific decision point during an action.
     
  • Popup_to_confirm_with_value

  • Create a dialog box in which you make a question whether the user wishes to perform a processing step with a particular object.  
  • Popup_to_decide

  • Create a dialog box in which you require the user between the two processing alternatives, or to cancel the action.
     
  • Popup_to_decide_with_message

  • Create a dialog box in which you inform the user about a specific decision point via a diagnosis text.
     
  • Popup_to_display_text

  • Create a dialog box in which you display a two-line message.  
  • Rfc_system_info

  • Fetch information from the current instance filling the structure FRCSI.
     
  • Rs_send_mail_for_spoollist

  • Send messages from ABAP/4 programs to SAPoffice. The structure SOLI may contain the message.
     
  • Rzl_sleep

  • Hang the current application from 1 to 5 seconds.
     
  • Rzl_submit

  • Submit a remote report.
     
  • Sapgui_progress_indicator

  • Set progress indicator on the left lower corner of the current window.
     
  • Sd_print_terms_of_payment

  • Format terms of payment according to base line date and payment terms.
     
  • So_wind_spool_list

  • Browse printer spool numbers according to user informed.
     
  • So_spool_read

  • Fetch printer spool according to the spool number informed.
     
  • So_user_list_read

  • List of all users filling the structure SOUD3.
     
  • Spell_amount

  • Return the amount in words filling the structure SPELL.
     
  • Th_saprel

  • Gather information from the current system including upgrade activities. It completes fields from the structure KKS03.
     
  • Th_server_list

  • Gather information of all instances filling the structure MSXXLIST.
     
  • Th_user_list

  • List of logged users filling the structure UINFO.
     
  • Th_user_info

  • Information about the current user. It completes fields from the structure KKS03.
     
  • Th_wpinfo

  • List of work processes filling the structure WPINFO.
     
  • Ws_upload

  • Transfer files from the frontend to the application server.
     
  • Ws_download

  • Transfer files from the application server to the frontend.
     
  • Ws_excel

  • Download files at the frontend in excel format.
     
  • Ws_execute

  • Execute an external program on the presentation server.
     
  • Ws_file_delete

  • Delete file at the frontend.
     
  • Ws_volume_get

  • Get the label from a frontend device.
     
  • Ws_msg

  • Create a dialog box in which you display an one-line message.

Wednesday 5 October 2011

SAP R/3 Troubleshooting



  • System gets stuck

  • It happens mostly when archive area is overloaded. Run the program brarchive with deletion option to release disk space.

  • Short dump

  • Not always the problem is technical. Try to create all SAPoffice users through transaction SO32 (create all SAPoffice users) and review your application data carefully.

  • Field exits are completely ignored

  • Make sure your SAP profile parameter contains the option abap/fieldexit = yes.

  • Transaction SE16 (table contents) does not work properly

  • Make usage of the menu option to regenerate the display program. You can also try changing key words according to field names. Choose Option -> Parameters users.

  • Rollback segments are too small

  • Before increasing up the rollback segment size you should verify your programs. Very often the problem belongs to them.

  • Files for rollback segments are already enormous

  • Check the rollback segments configuration. It has to match the allocated area on tablespaces. Changes have to be done using Oracle tools.

  • Extended help under windows does not link correctly

  • Check the file sapdoccd.ini under your presentation server. It must be present in the main windows directory and should assign to help files directory.

  • Release procedure with classification does not work

  • As a matter of fact you are not the only one to notice it. It hardly works. Before using release strategy you should apply all notes on OSS. Pray might be useful too.

  • Transport area is overloaded

  • The command tp clearold «SysID» cleans up the transport area according to parameters previously set on the plain file TPPARAM.

  • Instance does not establish communication

  • Shutdown the whole system and check the Interprocess Communication Facilities. Any references should be found. Either the command IPCS (UNIX) or showipc «INSTANCE NUMBER» (SAP) show all message queue, semaphore set and shared memory identifier. Before trying again you have to remove them using the command IPCRM (UNIX) or cleanipc «INSTANCE NUMBER» (SAP).

Sunday 2 October 2011

SAP Tips and Tricks - 2


  • General command field formats
  • /nSkip to the next record if you are processing one batch input session 
    /bendCancel a batch input foreground process 
    /nendClose all R/3 sessions and logoff 
    /nxxxxCall the transaction xxxx in the same session 
    /oGenerate a session list 
    /oxxxxCall the transaction xxxx in an additional session 
    /iDelete the current session 
    /hTurn the debug mode on 
    /$tabReset all buffers (for System Administrators) 
    /$syncSynchronize instances buffers (for System Administrators)

  • Report command field formats
  • %priPrint the current report 
    %pcDownload the current report 
    %scCall the find function 
    p+Go to the next page 
    p-Go to the previous page 
    p++Go to the last page 
    p--Go to the first page

  • Helpful reports
  • RSCLTCOPCopy tables across clients 
    RSAVGL00Table adjustment across clients 
    RSINCL00Extended program list 
    RSBDCSUBRelease batch-input sessions automaticly 
    RSTXSCRPTransport SAPscript files across systems 
    RSORARELGet the Oracle Release 
    RGUGBR00Substitution/Validation utility 
    RSPARAMDisplay all instance parameters 
    RSUSR003Check the passwords of users SAP* and DDIC in all clients 
    RSUSR006List users last login

  • Meaning of info structures' first letter
  • APricing 
    BOutput determination 
    CAccount determination 
    DMaterial determination 
    ERebates 
    FIndex 
    GListing and Exclusion 
    HBatch determination 
    IProfile determination 
    SStatistics 
    XStatistics extra

  • Unconditional mode when importing or exporting a request/transport

  • Run the command R3trans -u under user «SysID»adm.
     
  • Reapplying hot packages

  • If you accidently applied hot packages out of sequence for instance. Use the transaction SM31 to modify table PAT03. You have to choose the desired patch and click on delete entry.
     
  • Main return codes of tp program
  • 0Successfully done 
    4Warnings occurred 
    8Errors occurred 
    12Fatal errors occurred 
    16Internal errors occurred

  • Scheduling of system maintenance jobs
  • RSBTCDELClean the old background job records 
    RSDBCREOClean batch input session log 
    RSPO0041Removing old spooling objects 
    RSSNAPDLClean the old ABAP error dumps

  • List of most used SAP extensions and their components
  • CUST1MENUS000+C01Customer option in the Office menu 
    CUST2MENUS000+C02Customer option in the Logistics menu 
    CUST3MENUS000+C03Customer option in the Accounting menu 
    CUST4MENUS000+C04Customer option in the Human Resources menu 
    CUST5MENUS000+C05Customer option in the Information Systems menu 
    CUST6MENUS000+C06Customer option in the Tools menu 
    CUST7MENUS000+C07Customer option in the System menu 
    ZXUSRU01Exit_saplsusf_001At login time 
    SAPMF02DExit_sapmf02d_001When saving customer master data 
    SAPMF02KExit_sapmf02k_001When saving vendor master data 
    M61X0001Exit_saplm61c_001When processing MRP planning 
    M61X0001Exit_sapmm61x_001When processing MRP planning 
    FYTX0001Exit_saplv61a_001Modifications in pricing procedures 
    MBCF0002Exit_sapmm07m_001Checks for materials documents 
    SDVFX002Exit_saplv60b_002Link between SD and FI documents 
    M06B0003Exit_sapmm06b_001When saving MM documents

  • Before going live

  • It is highly advisable to increase the next extend´s size of some tables and their indexes even before initial loadings
    FIBKPF, BSEG, BSIS, BSAD, BSAK, BSID and BSIK 
    COCOEJ, COEP, COKS, COSS and T811* 
    AMANL* 
    MMMKPF, MSEG and BSIM 
    SDVBAP, VBAK, VBEP, VBPA, LIKP, LIPS, VBRK, VBRP, VBKD, VBUK, VBUP and VBSS 
    PPRESB and MDTB 
    Accross moduleATAB, TST03, TSP01, MCSI, KNVP, ACCTIT, COEP, APQD, RFBLG, CDCLS, SDBAD and from S000 to S999

  • Locking the whole system

  • Using the command tp locksys «SysID» only the user SAP* will be allowed to login. The command tp unlocksys «SysID» cancels the lock.
     
  • Connection between SAP R/3 and operating system

  • The command sapevt can be used to trigger an event from the operation system. Thus, a job previously defined within R/3 will be released.
     
  • SQL code help

  • Run the command oerr ora «error number» under user ora«SysID».
     
  • Oracle import and export explanations

  • Run the command imp help=yes under user ora«SysID». This format can also be used with expimpst, and expst.

CIN configuration in SAP SD

CIN configuration in SAP SD In his video you will see the concept of CIN and step by step Configuration in SAP SD Also see ...