E- Recruitment transaction PFAL transfer of data

Hi
I hope someone can be of help.   We have ECC6 and Erec 603 and need advice on running transaction PFAL.  We have set up the necessary links and ensured employees have infotype 105 for erecruitment.  We need to bring the data over to erec.  I have checked threads and found useful information concerning CRM but wondered if the data transfer is the same for Erecruitment.  CRM data transfer thread recommended the following:
-first move all the O in update mode with filter 1000 infotype through pfal
-then move all S in update mode with filter 1000 infotype through pfal
-then move all C in update mode with filter 1000 infotype through pfal
-then move all P in create mode (maintain filter of bd64 of infotype 1,2,6,105,1001) at this time use pfal - check if hrp tables are updated at that time.
-then move all O in crete mode use pfal
-then move all S in create mode use pfal
-then move all C in create mode use pfal
We want to take Organisational units, positions, jobs, person, qualification group and qualifications (O,S,C,P,Qk and Q).
Also there are date parametres etc to be completed should this be set to 'All' or today??
Many thanks
Julie

Hi Julie:
For the distribution model of ECC to E-Rec, you're right that you'll want to include object Q and QK (assuming you intend for your company's qualifications to be available in recruiting and for when requisitions are created, the related qualificaitons show up).
ALE is generally the same from ECC to CRM as it is to E-Rec, especially on the sending side.  When you PFAL, it's up to you on what you want for the date range.  'All' will obviously get you everything, but if you've got a lot of junk data in the past, it's gonna come over.  On the flip side, if you just to 'today', you'll miss future dated changes.  'All' is probably the best bet, but if you ask me, it's a judgement call depending on the company.
So you've set up your distribution model (transaction BD64) and your partner profile (transaction WE20) already, right?  If so, you should be cool to send off your data the first time from ECC using message type HRMD_ABA.
Good luck and let me know if that's not clear.
Thanks,
Chris

Similar Messages

  • Infotype Data Upload through transaction PFAL

    Hi All,
    Is there any option to distrubute data infotype wise in the transaction PFAL, i.e., i want to move the data into a particular infotype only.

    Hi
    Make sure the structure that you are using in the upload is the same that you have defined in your LSMW and may be in the same order. Also the fields of the structure defined are correctly mapped to your Batch input recording.
    In this way you should not get any formatting error.
    Thanks
    Nikhil

  • Transaction PFAL for ALE HR data distribution

    Hi Experts,
    We're facing a problem using transaction PFAL for HR distribution to our RPM system. We have our HR data defined in the ECC system but yet, when we run the transaction we get the message No data selected for distribution
    Any idea on which customizing may be missing?
    Thanks!
    Neil

    Hi Neil Billqvist,
    First you must be sure you used the right options in PFAL before going over to missing customizations. Maybe no data was found because wrong options were informed. I don't know what you are integrating with HR, but there is a useful building block about HR ALE distribution. Maybe there you'll find what's missing.
    [SAP Best Practices D59 - HR Integration to Project Resource Planning|http://help.sap.com/bestpractices/BBLibrary/documentation/D59_BB_InstallGuide_EN_UK.doc]
    Also check...
    [ALE QuickStart for Distributed HR|help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEHR/CABFAALEHR_ALE_QS.pdf]
    [Distributing HR Master Data and Org. Structure to CRM via ALE|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30139fb0-360c-2a10-1e9f-9d5417754983]
    Regards,

  • Sending IDOCS through transaction PFAL

    Hi,
    We have a requirement to send idocs through transaction PFAL for a set of PERNRs for all infotypes.What is the way to go about this?
    Thanks ain Advance!
    Regards,
    Nejuma Iqbal

    hi
    you cannot send IDocs thru PFAL transaction.
    you can send HR Master Data thru PFAL.
    yes you can send the Pernrs as they are Components of Organizational Elements.
    Here is the Procedure to send Personal Numbers:
    1.Execute the transaction PFAL.
    2.Give the object type as P.
    3.Give the Pernr values in Object ID field
    4.Select the transfer mode as Update
    5.In the Receiving Partner give your receiver name
    6.Give the message type as HRMD_A in the Message Type field.
    7.Dont change the remaining values.Keep it as such.
    8.Execute the Program.
    Also keep in mind that while sending the HR data you need to follow the certain sequence
    unless otherwise your data wont be replicated successfully.
    Here is the sequence O,S,P and C.
    Means before sending P  you should send O and S.
    Cheers,
    Abdul Hakim
    Mark all useful answers..

  • Issue in transfer of data from ECC to APO

    Hi All,
    I have a requirement of transferring data from ECC to APO. I am using EXIT_SAPLCMAT_001 fro this purpose. The problem is, I need to transfer the data of a field that is not present in cif_matloc but present in /sapapo/matloc.
    How should I proceed...Please help....this is an urgent requirement
    Thanks & Regards,
    SriLalitha

    Hi,
    you may want to go to the transaction /SAPAPO/SNP_SFT_PROF
    Determine Forecast of Replenishment Lead Time
    Use
    In this field, you specify how the extended safety stock planning determines
    the forecast of the replenishment
    lead time (RLT). The following values are available:
    Supply Chain
    The system determines the RLT forecast using the supply chain structure by
    adding the corresponding production, transportation, goods receipt, and goods
    issue times. If there are alternative procurement options, the system always
    takes the
    longest
    option into account.
    Master Data
    The system determines the RLT forecast from the location product master
    data.
    Master Data/ Supply Chain
    First, the system determines the RLT forecast from the location product
    master data. If no RLT forecast can be determined, the system determines the
    forecast using the supply chain structure (as described under
    Supply
    Chain
    Dependencies
    You can retrieve the replenishment lead time forecast yourself by using the
    GET_LEADTIME
    method of the Business Add-In (BAdI) /SAPAPO/SNP_ADV_SFT.
    Replenishment Lead Time in Calendar Days
    Number of calendar days needed to obtain the product, including its
    components, through in-house
    production or external
    procurement.
    Use
    The replenishment lead time (RLT) is used in the enhanced methods of safety
    stock planning in Supply Network Planning (SNP). The goal of safety
    stock planning is to comply with the specified service level, in order
    to be prepared for unforeseen demand that may arise during the replenishment
    lead time. The longer the RLT, the higher the planned safety stock level.
    Dependencies
    The field is taken into account by the system only if you have specified
    master data or master data/supply chain in the RLT: Determine
    Forecast field of the safety stock planning profile used.
    Hope this helps.
    The RLT from ECC is in MARC-WZEIT which is transferred to APO in structure /SAPAPO/MATIO field CHKHOR.
    May be if you maintain the setting in the profile, you may get the value in RELDT.
    Thanks.

  • 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 you’ll 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 don’t 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

  • EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

    Hi,
    I'm trying to various infotype 2001,2002,2006 ecc to another SAP system via ALE and since they are not part of message type "HRMD_A" I have created the extension ZHRMD_A06. I've already created the new segments(we31) and put these segments (with names Z1P2001, Z1P2002 ecc ecc) into the extension(we30). And I've assigned the extension to the message and basic type (we82).
    The new segment are processed correctly in the idoc creation via transaction PFAL, but via transaction BD21 i meet the abend message : B1 070 - Internal Error : program....command... for argument Z1P2001 (for example)
    In other words, BD21 do not process the custom segment but the PFAL yes...how it is possible?
    I've activate the change pointer in every customizing table intersting.
    Many thanks in advance for any reply
    Achille

    unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that
    are between the structures i must send in the other system sap.
    Ok, I have never delt with Time data in HRMD_A. Probably this is the case then
    Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems
    all correct!!
    By checking Filters I mean that confirm if you have added Time Infotypes there (just
    making sure). If data is appearing in BDCP2 that means there is no problem in Change
    pointer creation, Just ruling out possibility.
    Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments)
    is created without problems and in the BD21 no??? This is very strange
    1) Well BD21 uses the Function module (TBDME for HRMD_A) which read change pointers and
    create IDOCs. So now if you have extended Segment you have to add your population code
    here somewhere.
    2) PFAL is Push program, my assimption here is you have wriiten some piece of code to
    populate Additinal segments data here? Otherwise IDOC will not be populated
    automatically.
    Let me know what you think.

  • To transfer the data Cross the systems why we are not using BAPI Method?

    Hello All,
    To transfer the data Cross the systems why we are not using BAPI Method? why we are using only ALE/IDoc's?

    Hi Naveen,
       Listing down those I know -
       1. Master data is expected to be changed/created less frequestly.
       2. Transactional data is expected to be chnaged/created more frequestly.
       3. Transactions to create/change/display master data do no have message control integration, since you are not supposed to print/fax/mail master data to your partners.
       4. Distribution of master data in generally supposed to happen within Enterprise boundry and typically you will have one central server maintaining master data which will be distributed to multiple downstream operation system (Some thing where MDM fits). So ideally when distributing master data using ALE you will be sending it to multiple systems.
       5. Distributing transactional data PO/SO etc is same as sending fax/print which fits with the requirement of message control.
    Hope this helps,
    Regards,
    Sanjeev

  • Transfer Master Data Rate Routing

    Hello Gurus,
    We need to transfer Master Data (Rate Routing) with ALE. We already configure the ALE connection. We need to know which is the Process Code in the Inbound Table.
    Anyone can help us, please.
    Thanks in advance.
    Best Regards.

    Check this link
    http://help.sap.com/saphelp_47x200/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm
    For BOM and materials there are transaction codes...but i could not get for WC and Routing...

  • Error in transfer applicant data to PA30

    Hi  Friends
    When i am transfer applicant data to PA30,
    the error message come " maintain applicant activity error"
    i had check all the configuration and maintain
    also check all the post on the SDN related to transfer applicant data.
    but still i am facing problem.
    can anybody tell me how come out from this issue
    thanks and regards,
    urvashi chaudhari

    Hi Uravashi,
    Please goto transaction code PB 60 and check if the activities are maintained for an applicant. Delete all unwanted entries and again execute an action "Prepare for Hiring". In this step, after saving the first screen, one more pop up comes for applicant activity. If you have any specific activity then specify it here or simply click on enter.
    Once this is done execute the transaction code PBA7 to transfer the applicant data to PA.
    You have mentioned something about PA30 in ur last message. I hope it was a typo error.
    Thanks!
    Best Regards,
    Chetan Shriraj Wahane

  • I would like to transfer all data from my iPod classic to my new computer with windows 8.1. My old computer's cpu died. Utilizing iTunes which only allows iTunes albums purchased at iTunes store. The cd's were loaded via iTunes originally.

    I would like to transfer all data from my iPod classic to my new computer with windows 8.1. My old computer's cpu died. Utilizing iTunes which only allows iTunes albums purchased at iTunes store. The cd's were loaded via iTunes originally.

    Install disk drive from old computer in an external enclosure.
    Then copy the complete iTunes library from the disk drive to the disk drive in the new computer.

  • How do I transfer my data from damaged computer to my new itunes library on my current functioning computer. My data plan has a very limited band width cap ( I live in rural Alberta

    Hello: following computer malfunction,I purchased a new computer and downloaded itunes. when I try to sync my purchased data on my ipad I am asked to delete data from previous library. The first library has all of my stored data. How do I transfer this data to my new itunes library? . I cannot use the cloud as my data plan has a limited band width cap ( I live in rural Alberta , northern).My library may be on my tera drive, but then how do i delete this library once I transfer the files, that is if i am able to locate them ? this is a question for all itunes lovers, I love it when i know how to use it, so far not computer literate to loving it! thanks so very much for considering this problem.

    pervoskia wrote:
    Hello: following computer malfunction,I purchased a new computer and downloaded itunes. when I try to sync my purchased data on my ipad I am asked to delete data from previous library. The first library has all of my stored data. How do I transfer this data to my new itunes library?
    Copy the entire /Music/iTunes/ folder from old computer to new computer.

  • The "infallible" backup system crashes and burns; how to transfer the data?

    After five years of exemplary, error-free service, my old Powerbook G4 1Ghz finally crashed during a backup to an external hard drive. I just bought a new Macbook Pro (arrived September 16th) and want to transfer the data from the old Pro to the new Pro. Herein lies the complex problem, and Migration Assistant and a firewire cable won't solve it.
    When the old Pro died, I was maintaining what I believed to be an infallible backup system (ha). I did nightly backups to two different external hard drives; one was a USB LACIE drive, the other a firewire LACIE drive. I used Carbon Copy Cloner to do a merge contents backup on the USB drive and a file-level bootable clone to the firewire drive. Surely nothing could go wrong. Oh, one only needs to think of the Titanic and say, “Something did.”
    The old Pro could only backup to the USB drive when using an express card that added USB 2.0 connections (the old Pros have USB 1.1 and they’re too slow). But whenever the express card was plugged into my old Pro and it fell asleep without my first powering the card off, the computer crashed. This was no problem; I just powered off the card before putting it to sleep and ignored the fact that the computer on rare occasion acted buggy with the USB express card plugged in. Well, on the fateful night in question, the computer did its backup to the USB drive and then fell asleep while it was still plugged in (this is what its energy saver told it to do, unfortunately). When I tried to turn the computer back on, a black box appeared in the upper left hand corner with a bunch of random-seeming white text and the concluding message, “Waiting for remote debugger.” The computer was frozen and a cold reboot was the only option.
    My old Pro would never be the same again.
    I tried to boot it up. Sometimes it did so, but then would suddenly show a red screen and crash. It kept crashing, sometimes just powering off immediately. So I brought out good old Disk Warrior, booted up with that, repaired permissions, repaired disk, and rebuilt the directory. I also booted up with the Tiger OS X install CD and fixed permissions that way just for good measure. The computer then started up fine. I thought I was back to normal! Celebration time! Not. The USB drive that I had backed up to would not mount anymore. So I, seeing that the computer appeared to be back to normal, just plugged in second external hard drive--the firewire--and began the bootable clone. It delved into making the clone without a hitch and I went off to work happy and content that I would have an up-to-date backup soon.
    Lo and behold, when I came back from work, the backup to the firewire drive hung midway through. It had done nothing but wiped the entire drive and copied about 500 mb of data to it before freezing. I tried again several times and, believe it or not, only got vastly improved results when the offending express card was actually plugged into the computer. By this mysterious and probably risky method, I was able to get some data off. But only about 1/10 of the whole. The old Pro always would crash before more than 5 gigs of data or so can be transferred.
    Starting from around that time, the offending old Pro began to exhibit hideous popping, gurgling, grating, clicking, swiping, and other sounds from the left hand side of the computer—where I imagine the hard drive is. These sounds can be quite loud and sometimes even sound like tempered UFO tones beamed down to the computer. Sometimes they aren’t present at all and the computer acts fine, until a certain file or folder is accessed, and then they start again and the computer hangs, going from fine to disastrous in an instant.
    I took out the offending express card and launched it away and took the USB drive and put it on another computer. It still would not mount. I finally got it to unlock (it’s a fingerprint-access safe drive) and ran Disk Warrior on it and was able to get as much data off it as I could. But it appears that a huge chunk of data was simply missing from the drive, whether from Disk Warrior having to delete data when it rebuilt the directory or from damage when the computer died while backing up to this drive, I don’t know.
    So now I went from a supposedly infallible backup system of two rotating external hard drives to potentially losing 5 years of utterly critical work!
    I tried starting up the old Pro in target disk mode with my new Pro. At first, this appeared to have very promising results because there was no grating or popping sounds from my old Pro when I did this. I began a data transfer with glee. But no luck; the old Pro always eventually hangs and the new Pro doesn’t even recognize it (the icon for the old Pro disappears as if I unmounted it).
    Sometimes the Old Pro can still boot up and seem to act fine; it can sit like that indefinitely, I'd guess; but if the disk is actually read and written to enough, it always fails. I am using it as little as possible now (i.e. not at all) so as not to exacerbate the problem any more than it already has been.
    Two quick notes that might further explain the situation: two weeks before the crash happened, I used iDefrag to defragment the drive. The night before the crash happened, I did a lot of work on my computer while on a bumpy trip on the Long Island Railroad. The computer acted fine throughout all this, but perhaps the bumpiness or the defragmentation contributed to this problem.
    I must get the data off. This dead/dying hard drive doesn’t just contain mere photos and music libraries and nifty applications. I’m talking completed and incomplete novel manuscripts, lecture notes, lesson plans, published and to-be-published articles, a massive thesis, and much more totaling literally thousands upon thousands of pages and representing more than 5 years of graduate and professional research and work. For me, the stakes are critically high. Thank you for reading this Hero's Journey of a post.

    Good news!
    Imagine a Venn diagram with four interlapping circles. The circles are:
    1. Catastrophically exploded hard drive
    2. Catastrophically annihilated external hard drive used for incremental backups
    3. Catastrophically wiped cleaned external hard drive used for bootable clones
    4. Email, CD, and iPod backups
    With a little shake, rattle and roll and other craziness you do with a hard drive with failed bearings, I got #1 working briefly, thank goodness.
    With Disk Warrior and figuring out how to surpass a fingerprint-activated security feature, I got #2 working in a limited fashion.
    With some workarounds, I got some use out of #3.
    #4 just is.
    The interlap of these 4 things produced about 95-99% or so of my data, including all critical items. It was a disorganized mess I just spent two days organizing, but I am back up and running without having to use expensive data backup services. I am slightly bothered by that slight bit of missing data, but from what I can tell, it amounts to nothing more than a brief sketch of a lesson plan, a song or two from the iTunes store, and maybe a handful of attachments. Nothing to spend big bucks recovering, in other words.
    Now I will substitute my "infallible" backup system with a new one:
    1. Time capsule/time machine
    2. Complete online backups with Mozy
    3. Occasional bootable clones to the external hard drive I have that didn't get damaged.
    I think this will be the ticket!
    Thank you all.

  • Table for  the PO Date and Stock Transfer Order Date of a material no

    Hello Everyone!
    I am having a requirement where I want both the Purchase Order Date and Stock Transfer Order Date of a perticular material no.
    On the basis of difference of these two dates I want to find out the period for which the material was present in supplying plant.
    I am not getting the table through which I can get these two dates for a material.
    Please help me out.
    Its urgent.

    hi,
    see these tables:
         EKKO – Purchase Order Header Table
         EKPO – Purchase Order Item  Table
         EKBE – PO History table.
    reward if its useful

  • How do I transfer my data to my new macbook pro using an external hard drive?

    I've already set up my new MacBook Pro is my issue. It asked me if I'd like to "Migrate" my stuff or use an external hard drive etc but at the time I didn't transfer my data from my old MacBook yet. I was going to manually do it later as I had to wait for my External hard drive to back my old Mac up. Now it's that time and I have no idea how to do it. I believe I've researched best of my ability.
    I feel like I'm asking a pretty dumb question. If I were to just drag all my programs out like my Adobe Suite on to my new macbook pro would that work? I feel like that's just too easy and incorrect. Please and thank you.

    The Adobe suite can be downloaded free, you dont have to copy it at all, under standard CS6 Adobe rules, if you own the suite, you get 2 computers "activated at any one time"  Make sure, if youre not using the older computer, you deactivate the software under the HELP menu in Adobe.
    format the new drive in disk utility ......APPLICATIONS.....UTILITIES.....DISK UTILITIES.......select the external drive and format (if its new and empty!!!) under the ERASE button with Mac OSX extended journaled
    copy all your important stuff from older computer , pics, files, documents, personal anything.
    most of you apps, i ASSUME you bought in the (other than Adobe software, or Office suite, etc etc,..... obviously) in the MAC APP store, so you can reload them on the new computer without copying them , makes things very easy......just open APP STORE, and download what you already bought.
    really the only important things , is copy all important work files, documents, pictures, personal ABC...XYZ......  obviously.
    the migration is about emails, contacts, etc etc etc, also data, just because you passed it by at the time doesnt mean you still cant do it,    go to the SEARCH at menu at top and type in MIGRATION ASSISTANT  to do it again , since you passed it by at first .
    the only thing you NEED / SHOULD copy is all your personal stuff........Applications need to be reinstall from either ONLINE download,.......or from the MAC APP STORE,........  you cant just copy the apps over (in most cases) and toss them onto the new computer
    Nahh, there are no dumb questions, just dumb mistakes because you DIDNT ask any questions, and we all make those here and there. 

Maybe you are looking for