What is the Successfull processed IDOC status number?

Hi Experts
What is the Successfull processed IDOC status number?
arjent Please.
Thanks in advance
Sekhar

Hi Chandra,
Below are IDoc Process Codes
For outboud Idocs:
1 IDoc created
2 Error passing data to port
3 Data passed to port OK
4 Error within control information of EDI subsystem
5 Error during translation
6 Translation OK
7 Error during syntax check
8 Syntax check OK
9 Error during interchange handling
10 Interchange handling OK
11 Error during dispatch
12 Dispatch OK
13 Retransmission OK
14 Interchange Acknowledgement positive
15 Interchange Acknowledgement negative
16 Functional Acknowledgement positive
17 Functional Acknowledgement negative
18 Triggering EDI subsystem OK
19 Data transfer for test OK
20 Error triggering EDI subsystem
21 Error passing data for test
22 Dispatch OK, acknowledgement still due
23 Error during retransmission
24 Control information of EDI subsystem OK
25 Processing despite syntax error (outbound)
26 Error during syntax check of IDoc (outbound)
27 Error in dispatch level (ALE service)
28 Not used
29 Error in ALE service
30 IDoc ready for dispatch (ALE service)
31 Error - no further processing
32 IDoc was edited
33 Original of an IDoc which was edited
34 Error in control record of IDoc
35 IDoc reloaded from archive
36 Electronic signature not performed (timeout)
37 IDoc added incorrectly
38 IDoc archived
39 IDoc is in the receiving system (ALE service)
40 Application document not created in receiving system
41 Application document created in receiving system
42 IDoc was created by test transaction
50 IDoc added
For Inound Idocs
51 Error: Application document not posted
52 Application document not fully posted
53 Application document posted
54 Error during formal application check
55 Formal application check OK
56 IDoc with errors added
57 Test IDoc: Error during application check
58 IDoc-Copy from an R/2 connection
59 Not used
60 Error during syntax check of IDoc (inbound)
61 Processing despite syntax error (inbound)
62 IDoc passed to application
63 Error passing IDoc to application
64 IDoc ready to be transferred to application
65 Error in ALE service
66 IDoc is waiting for predecessor IDoc (serialization)
67 Not used
68 Error - no further processing
69 IDoc was edited
70 Original of an IDoc which was edited
71 IDoc reloaded from archive
72 Not used, only R/2
73 IDoc archived
74 IDoc was created by test transaction
Regards,
Satish

Similar Messages

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

How to map journal fields and whats is the better process type

/Journal/JournalSuspenseCostCentre     NULL
/Journal/JournalBalancingCentre     Lookup from Organisation ID
/Journal/JournalMultiCompany     u2018Nu2019
/Journal/JournalBatchNumber     NULL
/Journal/JournalNumTransactions     Total number of /Journal/JournalLine transactions
/Journal/JournalBaseDRTotal     Sum of /Journal/JournalLine/JournalLineBaseValue u2013 Debit Values only
/Journal/JournalBaseCRTotal     Sum of /Journal/JournalLine/JournalLineBaseValue u2013 Credit Values only
How to map journal fields and whats is the better process type idoc/proxies?please let me know
Journal Line
Multiple journal lines per header:
Schema Element     Data
/Journal/JournalLine/JournalLineCostCentre     Bank account control Cost Centre
/Journal/JournalLine/JournalLineAccount     Bank account control Account Code
/Journal/JournalLine/JournalLineMoneyTotal     Transaction Line Amount
/Journal/JournalLine/JournalLineVolume     NULL
/Journal/JournalLine/JournalLineDescription     Payee Name
/Journal/JournalLine/JournalLineChequeBookReference     NULL
/Journal/JournalLine/JournalLineMatchField     Cheque Number
NB Contra accounting entries should be posted to:
Schema Element     Data
/Journal/JournalLine/JournalLineCostCentre     Bank account control Cost Centre
/Journal/JournalLine/JournalLineAccount     Bank account control Account Code
/Journal/JournalLine/JournalLineMoneyTotal     Transaction Line Amount * -1
/Journal/JournalLine/JournalLineDescription     Payee Name
/Journal/JournalLine/JournalLineMatchField     Cheque Number
/Journal/JournalPeriod     Current General Ledger Period
/Journal/JournalYear     Current General Ledger Year

It looks you are new to PI,
you have to develop scenario end to end, by creating source data type and target data type(if you have XSD's not required),then use Graphical mapping (message mapping) to map source and target structures.
Search in sdn for one end to end scenario you will understand easily
Regards,
Raj

What is the importance on BOM Explosiion number

Hi,
what is the importance of BOM Explosion number . can any one give me in detail in which context it is used.
second is valuation type is getting populated in components of a production order. from where this valuation type is flowing to the child components.
thanks in advance
madan mohan

Hi,
By means of Bom explosion number we can define a common explosion date for all BOM levels.
The system explodes the BOM that is valid on this date.
For multi level BOM lareger time intervals may exist between the explosion dates of individual assemblies.If the BOM's have changed mean time a situation may exist where by an assembly that is used repeatedly is produced with a different BOM structure.
Therefore the BOM should always be exploded with the same date.
Tcode MDSP
You need to enter fixed key date,plant material and the status whether active or inactive.
You can enter the BOM Explosion No in planned order or when creating PIR.
Regards,
nandha

What is the use of GUI status in Dialog programming

what is the use of GUI status in Dialog programming,, how can it be used there,, as screen are alredy defined..

Hi,
The use of GUI Status is that when we have to change some thing in Menu Bar, Toolbar and Function Keys. Say For Example we have to create any Custom Button in the application toolbar etc.
It can be used in Dialog Programming via defining the Status in the PBO module of the screen.
eq. created a screen 9000
          on clicking it->
                               PROCESS BEFORE OUTPUT.
                                         MODULE status_9000.
On double clicking on this "Module status_9000" - you can write "SET PF-STATUS 'STATUS_9000'".
Now u can create GUI staus with name "'STATUS_9000'".
Let me know in case you have any further doubts.
Thanks

What is the best process for conversion moving district data to city data?

Hi ALL,
I Need to write one conversion which will move the district field data into city field data in infotype 6..
It need to apply for only one Specific country which can be identified by Employee Personnel Area..and it should be apply for all active , Terminated employee as well...
What is the best process so that i can catpure all the data records of employees of the Specific country?
my approacH is..
LDB: PNP.
Start-of-selection.
RP_PROVIDE_FROM_LAST P0001 space pn-begda pn-endda.
check p0001-weks = '5200'.
rp_provide_from_last p0006 space pn-begda pn-endda.
Loop at p0006.
move p0006 to T_p0006.
if ort01 is not initial
Move P0006-ORT01 TO T_P0006-ORT02.
endif.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = '0006'
          subtype       = P0006-subty
   objectid      = P_record-objps
          number        = p0006-pernr     "employeenumber
          validityend   = validityend
          validitybegin = validitybegin
         record        = T_p0006.
          recordnumber = p_record-SEQNR
          operation     = 'MOD'
          nocommit      = nocommit
          dialog_mode   = '0'
        IMPORTING
          return        = return_struct
          key           = personaldatakey
        EXCEPTIONS
          OTHERS        = 0.
      Endloop.
Is this using Loop is fine? or Using PROVIDE * from p0006 between PN-BEGDA AND PN-ENDDA
ENDPROVIDE is fine?
Is my code is accurate...Bapi_employee enque bapiemployee_deque i will add apart from that is this code is fine for my requirement or any additional need to take care to capture all the employee data ?
Regards
sas

Hi,
Please use the following code: -
RP_PROVIDE_FROM_LAST P0001 space pn-begda pn-endda.
check p0001-weks = '5200'.
rp_provide_from_last p0006 space pn-begda pn-endda.
provide * from p0006 between PN-BEGDA AND PN-ENDDA
move p0006 to T_p0006.
if ort01 is not initial
Move P0006-ORT01 TO P0006-ORT02.
endif.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = '0006'
subtype = P0006-subty
objectid = P_record-objps
number = p0006-pernr "employeenumber
validityend = p0006-endda
validitybegin = p0006-begda
record = p0006.
recordnumber = p0006-SEQNR
operation = 'MOD'
nocommit = nocommit
dialog_mode = '0'
tclass = 'A'
IMPORTING
return = return_struct
key = personaldatakey
EXCEPTIONS
OTHERS = 0.
endprovide.
Hope this will help you.
Thanks & Regards,
Gaurav

What are the advantages of idoc compare to flat file. how data is secure

what are the advantages of idoc compare to flat file. how data is secure in idocs compare to flat file

Hi Ramana,
In simple words, Main advantage with idoc over flat file is security....
I will explain you some scenario here U got a flat file with all the data...Now u r having the flat file if you want u can modify the data in it, or somehow any one can modify the data in it if they were able to access this file. That means u maintained the file in the presentation server
One level of higher security to the above level is maintaining the flat file in application server, at point also even though lot of people r not having the access to that file, super user who is having the access may modify the data or delete the data from it rite....
so in both of those levels u don't have 100% security...
So there come to the picture of idocs, Idocs simply data carriers, those r generated by a program but not manually...data will be divided into number of segments based upon ur program. So manually its not so easy to modify the data in these idocs. If any changes to be made in the data then u have to modify the data in the application and then u have to update the idoc or you have to generate the new idoc with that corresponding data. so in this case not even super user can manipulate the data directly in the idoc....
I think u got my point what I mean to say.....
If you find it useful mark the points
~~Guduri

What is the diffrence btween IDOC and BDOC?

what is the diffrence btween IDOC and BDOC?

Hi,
In short Idoc is an Intermediate Document and Bdoc is an Business Document.
Data can Be Transferd from Sap to Non Sap using Idoc where as we can transfer
data between sap to sap in Bdoc.
IDoc
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions
BDOC
BDoc is a business document which is technically similar to an IDoc. BDocs are used to communicate data between two systems.
BDocs come in two types. One is the message BDoc (MBDoc) and the second is the Synchronizing BDoc (SBDoc).
MBDoc is used for replicating the data between SAP CRM and SAP R/3
SBDoc is used for replication and realignment between SAP CRM and mobile clients
som times SAP will be integrated with som other third party systems
ex SAP with BAAN here we should comunicate one to other systems
here we can integrate using EDI technology in this the formate of data will be in I DOCS EX :EDI is a bridge between 2 systems .I doc is a container to transfer data from one sys to other
this Idocs we can use in ALE technology also
BDoc is called Business Document,
BDoc represents data in a structural format. This sturctural architecture is use to either input data to system or send data to other system.
BDocs are data carrier that can either collected in system(Inbound) or can be send out of system(Outbound)
Please refer following link:
http://help.sap.com/saphelp_crm40sr1/helpdata/en/ec/8d7e3a7e760b55e10000000a114084/content.htm
Thanks,
Medha.

What are the oracle processes involved in Data Guard Operation

Hi All,
I have a Primary and secondary physical standby database.
I want to know what are the oracle processes involved in the synchrnization between primary and secondary.
Thanks
Santosh

The best place to get this information is Data Guard Concepts and Administration Guild
The link for 10g Release 2
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14239/concepts.htm#i1039416
The link for 10g Release 1
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10823/concepts.htm#1039415
The link for Oracle 9i
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96653/concepts.htm#1027493

What is the meaning of Recorded Status in SXMB_Moni ?

Hi Experts
What is the meaning of Recorded Status in SXMB_Moni ?
it showing green flag with recorded status
Thank You
G.Praveen Kumar
Tecnics Integration Technology .
PI Consultant

Hi Nilesh/Divya,
Goto SMQR and activate corresponding queue
What if the Queue is registered....do registered Queues not face this type of problem??
Regards,
Abhishek.

This is probably a stupid question, but what does the red circle with a number in it mean on iCal? It looks just like the emails notification. I do not have anything do or up in my cal.

This is probably a stupid question, but what does the red circle with a number in it mean on iCal? It looks just like the emails notification. I do not have anything do or up in my cal.

Actually, another person on the "more like this" had the right answer. It meant I had a notification for an invite that I needed to respond to.
Hope this helps you as much as it helped me.
D

What is the current magic mouse model number?

What is the current magic mouse model number?

It’s MB829LL/A; the fourth and fifth letters may vary by country.
(116783)

What is the system variables of document number in General Ledger PLD?

Dear all,
Would anybody kindly tell me what is the system variables of document number in General Ledger Print Layout Designer?
The default print layout use transaction number (system variables 272), however, my client wants document number to be displayed in the transaction number column.
Regards,
Simon Chiu

Hi
The only list available for Supported variables is for the version 2007A and for some specific localizations like Brazil and India.
For the 2007A version the list is available in the following link:
http://service.sap.com/smb/sbo/pld
'How To Use the PLD Variables File in Release 2007 A '
But in general the variables are for documents not for reports.
In this case I believe there's no variable and you may need to fill a requirement in the Forum for that.
Paulo Calado
SAP Business One Forums Team

I know it is stupid but what is the word processing program on the ibook software?

I know it is stupid, but what is the word processing program installed on the ibook g4?

Hi, Wayne. Welcome to Apple Support Communities.
Is AppleWorks installed? It's what I use, and came on many iBook models.
TextEdit Is a rudimentary word processor, and is included with Mac OS X.

What is the Learning Process for SAP Business ByDesign

Hi Experts,
What is the Learning Process for SAP Business ByDesign
Prashant Kapoor

HI prasanth,
SAP-ByD always updated day to day. you can find here:
https://my020062.sapbydesign.com/sap/ap/ui/repository/SAP_BYD_WEKTRA/CP/sapLSUIContentPlayerTestPage.html?manifest=067D03A7602B1D490899DF46B5082089&COMPONENT=A1S_PDI&RELEASE=260&LANGUAGE=en&REGION=&INDUSTRY=&TASK=CR_VIEW&sap-language=EN
Note: do u want open the above link u might have a .net framework4.0 bcz this one silverlight application.
Best Regards,
Harish.y

What is the Successfull processed IDOC status number?

Similar Messages

Maybe you are looking for