Uploading Customer Master data using Direct Input Method

...Previous

Put the cursor on respective field and then click on Rule button.

 

 

Now after rule insertion, mapping looks like below.

 

Defined initial check rule for each and every field in the source structure which are used in the mapping and used conversion exit to provide leading zeros to the input field value for few selected fields where ever it is necessary.

 

Follow similar steps for rules button and choose this radio button.

 

 

Provided constants where ever necessary lime below

 

 

There are also few other possible features are available under Rule button which can be used according and effectively based on the requirement.

 

To ensure that we have done field mapping for each and every field which is present in the source structure and we have not left any field with un-mapping, we can follow below path to check.

 

These above are the basic steps which need to be considered while doing any LSMW objects.

Apart from this there are few sections available in the LSMW design where we can also insert some custom code to achieve few other things.

 

Below shown are the different processing blocks of a LSMW object.

 

One single record in the input flat file refers to one transaction in LSMW.And this one transaction contains data which bellows to different structure available in the standard program interface. Each structure got a –Begin of record and –End of record event, where we can write our custom code to manipulate the whole record. If we would like to skip some record of any transaction, we can write some custom logic here it self. Logic written here wont affect the while transaction but that specific structure record.

 

You can double click on the code section and Implement your new custom code.

 

Similarly we can write our custom code at –Begin of transaction & --End of transaction to manipulate the whole transaction record.

 

 

When all the records from flat file/or all the transactions at LSMW level got processed, the event

--End of processing gets trigger where we can write some custom code giving the summary of all transaction processing.

 

 

Errors will be calculated during each record processing stage if any and if any error is found then input data is not transferred to transaction level but error details will be provided at the end of processing.

 

Implemented logic to do date formatting as per the requirement. Used PERFORM F_GET_DATE to convert incoming date format MM/DD/YYYY to YYYYMMDD.So the perform we can call in LSMW level and the form routine can be written at –Form Routine—section. This routine is local to the LSMW object only.

For doing all these custom coding we can do data declaration in –Global Data—section.

 

You can make use of button   to change the layout

Click here to continue...

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image