How to upload the master data from legacy to SAP

Hi Frends,
how to upload the master data from legacy system to SAP System once the configuration is over.how to carry forward the open items of vendors and customers while uploading.who will upload functional consultantsor ABAPER.
please clarify me
Regards
Sap Guru

Hi ,
use LSMW or BDC for uploading Master & transaction data.
This work is done by the Respective Functional team.
Chandra

Similar Messages

Upload vendor master data from legacy system to internal table tcode xk01

through batch input program how to upload vendor master data from legacy system to internal table and then to SAP R/3 database(transaction XK01) by using recording method.

By learning the basics of BDC recording and the use of GUI_UPLOAD

Uploading the Master data From SCAT

Hi Experts ,
Can any one explain how to upload the mater data by using SCAT(In Step Wise).

SCAT (CATT)

How To Transfer the master data from R/3 to APO System

hi this is mohamed .i m new to APO..
can any one guide me the configuration for transferring the master datas to APO system.i m using scm 4.0 version..
Thanks in advance
Regards
Mohamed.

Welcome to SDN.
refer this link
creating integration model
Give ur mail id i will send the document which i have.
With regards.
Maya.

Uploading Material Master data from legacy system

Hi all,
do we have any sap defined bdc for material master data ,if no ho to do that can anybody explain me step by step procedure how to do that
Thanks in advance
Santosh R

Santosh,
Use BAPI as we already have pre-defined BAPI for material upload given by SAP.
<b>BAPI_MATERIAL_SAVEDATA</b>
Also check this BAPI in MM01 uploading for the complete code I have written.
Regards
Aneesh.

How do you validate transfer of data from legacy to SAP (Tcode: SQVI)?

Hello PP members:
I would like to know how to validate transfer of data from legacy to SAP
A friend of mine was telling it has to do with <u>SAP quick viewer(SQVI)</u> but could not able to much leads on it
I would be thankful if can provide insights into the subject
Thanks for your time,
Suren R

Suren,
Yes, you could create queries in SAP with SQVI and get the data in SAP. But you need to be aware of all the relevant tables in SAP.
For information for creating queries use link:
http://help.sap.com/saphelp_47x200/helpdata/en/05/2b1df9209411d6b1d500508b6b8b11/frameset.htm
For getting the relevant tables the easiest way is :
1) Goto Se16.
2) Choose F4,
3) Click on SAP applications and drill down to the relevanttable.
Hope this is useful. If yes reward poins and close this thread.
Regards
Ram

Upload the master data in abap-hr using Lsmw tool

Hi Friends,
Any one Help me How to Upload the Master data in ABAP-HR using LSMW.
In Recording what need to fill.
If any screenshots are availave please provied me.
Thanks and Regards,
Sai.

http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
Try this .....

*Journal Entries while uploading the vendor master data from legacy system*

hi SAP Folks,
can any one of you tell me the journal entries while uploading the vendor master data from legacy system to SAP system.
Eg: legacy system is having 10000 vendors list, 1 reconciliation account and $ 1000000. while uploading all these data from legacy system to SAP what are the journal entries we get.
thanks in advance.
Edited by: ravindranath manikonda on Nov 24, 2008 1:12 PM

Hi
you will be having only one entry logically
i.e. Opening Bal. clrng A/c Dr.
To Vendor A/c Cr.
regards

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

Upload GL accont master data from legasy to SAP R/3

Hello Gurus,
I have a requirement to write a BDC program for uploading GL account master data from legacy system to SAP R/3 database using FS00 transaction.Please can you help me with this?
Regards,
Kalpana.

Hello,
Goto Transaction SHDB, then create one new recording then do the simple recording and save that recording in one program and use as per your requirement.
you can also use existing program suggested by Rob.
Regards,
Sujeet

How to delete the Hierarchy data from Infoobjects.

How to delete the Hierarchy data from Infoobjects. In my case I had 300 records in the corresponding table of info object.
When i was trying to delete the hierarchy data, I am getting error message. "Some master data not deleted". Can any one tell me to delete all these records by using a program.

Hi
Go to SE11 and enter the hierarchy table name.
/BIC/H....(infoobject name)...and execute the table and select table entry and delete all....
Thanks
TG

Error while uploading HR master data from inQuality server

Hi, Expert. While uploading of MAster data from Developement to Quality by BDC. When program starts for Tcode PA40, selecting Hiring Action, it is goining to the Action Screen. Here while taking the position from HR template, it gives error as Position is not in Table T428B. Payroll area on the date (Date of original hiring, of the person) it is taking DM as defalt in place of our created Area and terminating. When i am trying entering the data manually, it is giving same error for Position. I am not able to upload the data. Kindly help me by suggesting me the correct sequence and steps for uploading the data. Correct answer will be provided with STARSSSSSS **. Regds Punit.

Have all your configurations been transported to Quality?
Have you created the positions before initiating BDC for Hiring?
Check Feature ABKRS in Quality. Is this same as in Development?
Is your BDC running OK in Development?
Regards,

Open hub Services - How to extract the master data related to a object ?

Hi Gurus,
I am implementing OpenHub services for our project, it's on BW 3.5, I have the list of required fields with which I am creating an InfoSpoke. Now I am stuck in some the info objects which are having master data associated with it.
Example : Business partner(BP) data, when I map the 0BP infobjects in infospoke it's extracting the BP ID (ex: CT065316,CT068638 etc) in flat file but I want the BP name, address & telephone number as well, which are coming from master data table. But I am able to map only 0BP infobjects as a part of ODS/Cube.
Can any one tell me how to get the master data extracted in the flat file with associated info object???
Answers will be highly appreciated.
Regards,
Kironmoy Banerjee
Edited by: Kironmoy Banerjee on Oct 1, 2009 3:34 PM

Hi Kironmay
Please follow the below mentioned procedure to create a transformation. This is applicable for BW 3.5 as well.
- Enter your infospoke in the edit mode.
- On the Transformation tab set the indicator for the Infospoke with Transformation with BADI so that the infospoke is activated.
- This will take you to the Addin implementation/BADI builder.
- Enter the short text/description for the implementation. The implementation name is always the same as the technical name of the infospoke
- The implementation of the BADI is always filter dependant.
- In the properties tab of the infospoke enter your infospoke under the Filter specifications.
If you do not specify an InfoSpoke under Filter Specifications, then this implementation is valid for all InfoSpokes. This means that this is called up for all InfoSpokes during the extraction.
- Activate your class
- From your interface tab page, double click on the Transofrm Method and you will arrive in the class builder page
- Here you can enter the code
- To do a look up of the master data you have to write a code similar to the one I've given below. This is just an example for looking up material master.
IF FLT_VAL = 'Your infospoke'.
T_DATA_IN[] = I_T_DATA_IN[].
Select zstd_cost from /bi0/pmaterial into table T_return
For all entries in T_DATA_IN
WHERE material = T_DATA_IN-material.
...Continue with your code.
Append output from T_return to your output E_T_DATA_OUT
- Activate your method. Return to the BAdI builder. Return to your InfoSpoke.
I hope this helps.
Thanks.

Uploading the master data.

Hi! SAP gurus
I need some help in uploading the vendor code from 20000001 server 1 to another server 2.
I have tried to do it but still unable to see in server 2.
Where the problem could be?
Please respond me immediately.
Thanx in advance

Hi Sushmitha
I think there are two options available to migrate master datas from one server to another.
1) ALE (Application Link Enabling)
2) LSMW
To know more about ALE, go through the link
http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
LSMW is you need to create a recording in the server in which you would like to upload the master datas.
Thanks
G. Lakshmipathi

How to Lock the master data. R/3 Conflict ESS

Dear Gurus,
Please guide me how to lock the master data for a nos of days(say 7 days).
Recently we had encountered an issue, related to ESS. While Uploading the Time data through t-code: PT60, our core team encountered a problem, that such and such employee number is locked.
While checking, they identified it, system shown error against those employees, who are accessing their ESS. We check and came to know they are accessing the master data by changing their personal record i.e. address.
Do we have any other provision to lock the master data without setting the control record to release for payroll.
Please help .

Create a custom transaction involving a custom views of table T7XSSSERSRV with the following field for each service
"V_T7XSSSERSRV-ISDISABLED"
when HR wants to lock it, the will enter this table and check this field.
this will disable the servcies in the front end.
Once the 7 days are over, HR will uncheck this field. this will re-enable the services in the froint end.
Hope this helps.

How to upload the master data from legacy to SAP

Similar Messages

Maybe you are looking for