Transfer of inforecord condition records through ALE

Hi,
I want to know how to transfer Info record condition types other than PB00 through ALE.e.g. FRA1,Z cond. types etc.
Thanks,
Kaveri

Hi,
Transaction VK13, you check if this one suits your requirement.
Thanks
Krithika

Similar Messages

  • Transfer of inforecord condition types through ALE

    Hi,
    I want to know how to transfer Inforecord Condition Types other than PB00 through ALE.For condition type PB00,we can use msg type COND_A & t-code MEK3.Similarly, what are the corresponding values for other condition types like FRA1 etc.
    Thanks,
    Kaveri

    Hi,
    If we are loading the conditions by IDoc type COND_A, we do not give the transaction code, instead we specify the table (like KVEWE = 'A' & KOTABNR = '025' for the Inforecords with plant level conditions), We give the condition records to structure E1KONP with condition PB00 as first condition followed by other conditions ( example RA00, RA01) in sequence as per the condition schema mentioned.
    So you can load the FRA1 condition the same way, just feed the LSMW the condition record FRA1after PB00.
    Hope this helps.
    Best Regards, Murugesh

  • Transfer of Classes( Classification data) - through ALE

    Hi experts,
    I am trying to transfer Classes from a 3.1i system to a ECC 6.0 system through ALE distribution.
    Almost all the classes got transferred but in a few of the classes, the status of the idoc remains at 64 - waiting to be processed.
    When I scheduled the processing of these idocs in background mode they result in a dump.
    Dump:
    The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
      caught in
    procedure "MAINTAIN_ALLO_VALUES_VIA_API" "(FORM)", nor was it propagated by a
      RAISING clause.
    This dump is happening because sy-index value is crossing 2147483647 ( which is the max allowed value).
    I could not find any relevant notes for it. Does anyone know what is causing this issue and how to correct it.
    FYI - There are around 3000 values attached to a characteristic which is attached to the class.
    Thanks and Regards,
    Karthik

    Hi Karthrik,
    Did you never get answer on this topic or did you make a request to SAP in the meanwhile? I got same dump and I am looking for solution, too.
    Br
    Markku

  • Transport Output Condition records with ALE

    Hi All.
    Does anyone know if its possibel to transport Output condition (mn01, mn04 etc) records via ALE between systems.
    It appears to be possible for normal condition records (VK01) but doesn't appear possibel for the output ones.
    Any ideas how to set this up so we don't have to manually create these records in all environments?

    Hi markjaneasl     ,
    Check any  message type existed for that or not. Better if you post in this ABAP forum.May be you will get proper replies in that forums. Explain the requirement little more.
    Regards,
    Madhu.

  • Standard Report for PIR /Purchasing inforecord condition records.

    Hi ,
    Anyone knows of any standard report for PIR condition records?
    Thanks
    Regards,
    Clarice

    hi,
    There is no specific condition report for the condition records but you can check the table for the conditions, those are KONP, KONH, KONV ...
    Hope it helps..
    Regards
    Priyanka.P

  • Transfer Custom OM Infotype data through ALE for HRMD_ABA Message type

    Hello Folks,
    I have created a Custom OM Infotype.When i run the PFAL transaction. All the standard infotype data is getting filled, but i dont see custom infotype data getting filled.
    Example: HRP9001 is the custom infotype.
    Please let me know the step by step process to populate the Custom infotype data in ALE Transfer.
    Thanks & Regards,
    Nishanth Kumar

    I think function module RH_MASTER_IDOC_DISTRIBUTE_HRMD shows some odd behaviour. It calls EDI_DOCTYPS_OF_MESTYP, which returns the name of the extension in an internal table named "doctyps". But later on, function module MASTER_IDOC_DISTRIBUTE is called with a structure "f_idoc_control". In this structure, the field "cimtyp" should hold the name of the extension, but it NEVER gets filled, although the value is present in doctyps-cimtyp.
    So what I have done, is to activate userexit #004, which is called just before MASTER_IDOC_DISTRIBUTE and modifies structure f_idoc_control, if desired.
    Call transaction CMOD and create a project in a non-SAP namespace: Zxxxx. The enhancement we need is "RHALE001" (HR-CA: Enhancement for ALE functionality in HR). One of its components is EXIT_SAPLRHA0_004, which consists of include ZXHALU08. In this include I called EDI_DOCTYPS_OF_MESTYP again to fill f_idoc_control-cimtyp.
    Here is my code for include ZXHALU08
    DATA: z_doctyps TYPE STANDARD TABLE OF edidocs WITH HEADER LINE.
    CALL FUNCTION 'EDI_DOCTYPS_OF_MESTYP'
      EXPORTING
        mestyp         = f_idoc_control-mestyp
      TABLES
        doctyps        = z_doctyps
      EXCEPTIONS
        invalid_mestyp = 1
        OTHERS         = 2.
    IF sy-subrc = 0.
      LOOP AT z_doctyps.
        f_idoc_control-cimtyp = z_doctyps-cimtyp.
      ENDLOOP.
    ENDIF.
    Hope this helps

  • How to get the exact time when condition records has been created?

    Hello All,
    Can anyone thorw some light on - how to find the exact time on which a particular condition record has been created?
    I have tried to get it from KONP {by inputting condition record number}, but unfortunately time is not tracked over there, but the date is tracked.
    Await your valuable inputs on the same.
    Regards,
    Hrishi

    Dear Hrishi,
    Try with this
    Go to display mode of the condition record through VK13 transaction from the condition record overview screen go to menu Environment >Changes>Click on Change report now system will take you to the Change Documents for conditions selection screen here you input proper selection data then execute now system will give the all the details here you can find the time also.
    I hope this will help you,
    Regards,
    Murali.

  • CRM TPM 7.0: Accruals amount is zero in the condition records

    Hi All,
    I am creating condition records through TPM, the amount value is getting populated correctly in the condition record, however, the accruals value is showing up as zero. Ideally, I wanted to have the accruals value same as the amount in the condition record. Can anyone suggest a solution on this?
    Any help in this regard is highly appreciated.
    Thanks in anticipation !
    Kind Regards,
    Neeraj

    You must be using Funds Management.  Zero accrual rate in ECC condition record is correct.

  • How to send inforecord conditions using ALE (message type COND_A)?

    Hi,
    I have sent Purchasing Inforecords through ALE using t-code ME18.
    Now, I would like to know how to transfer the conditions through ALE (message type is COND_A).
    Thanks a lot,
    Kaveri

    Hi,
    Please go through this thread.
    [Pricing Condition Records initial upload - COND_A]

  • Condition record data transfer

    I have a scenario where condition record data from ECC needs to be transferred to MDM.
    I can see COND_A01,COND_A02 idocs in ECC .Pl can you tell me which one is relevant for ALE data transfer.
    Is there any transaction/report (For example BD10 is used for material data transfer) which can generate idoc of condition record and distribute it to receiver
    Pl can you suggest on this.
    thanks,
    Sharada

    I think there is no standard program for distributing Condition records.
    As suggested by Eshwar use COND_A02.
    u are distributing only Condition records to MDM that means u have condition record repository over there.
    i don't know what is the mian program to create Condition Records .
    see is a way to attach output types to that and NACE configurations to distribute it.
    Suresh

  • Condition Record Price is not updated in Inforecord

    Dear Experts
    For a material , the price in the condituion record is maintained as below.But in the info record the value is showing as 14 , instead of 10 at present.
    Validity from      Validity to      amount
    3/2/2008     3/30/2011     14
    3/31/2011     3/31/2011     10
    4/1/2011     4/30/2011     14
    5/1/2011     12/31/9999     10
    please help how to get the condition record amount in Inforecord.
    Thanks
    chandra

    Hi Chandra,
    You should run the program "RM06INP0" with SE38 to update the latest prices in PIR.

  • FM to upload condition records into inforecord (ME12).

    Hai experts,
    Can any one let me know if there is a FM or BAPI which can be used to update/upload condition records into inforecord (Transaction ME12). I need to know it to write a program for mass change/adding of conditions for huge number of inforecords.
    A sample program would be more helpful for me.
    Thanks in advance.
    Matt.

    Hi,
    Please try given below code.
        CALL FUNCTION 'ME_INITIALIZE_INFORECORD'.
        CALL FUNCTION 'ME_DIRECT_INPUT_INFORECORD'
          EXPORTING
            activity         = 'V'
            i_eina           = ls_eina
            i_eine           = ls_eine
            i_no_suppose     = ' '
            i_vorga          = 'A'
          IMPORTING
            e_eina           = ls_eina_new
            e_eine           = ls_eine_new
          TABLES
            t_head           = lt_head
            t_line           = lt_line
          EXCEPTIONS
            textname_invalid = 1
            OTHERS           = 2.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ELSE.
          CALL FUNCTION 'ME_POST_INFORECORD'
            EXPORTING
              i_matnr  = ls_eina-matnr
              o_matnr  = ls_eina-matnr
            TABLES
              t_eina_i = lt_eina.
          IF sy-subrc IS INITIAL.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
              EXPORTING
                wait = 'X'.
    Regards,
    Narendra

  • Transfer of condition records

    hi guys,
    I have  couple of questions regardign the transfer of the conidtiopn records from R/3 to CRM
    IF we trying to create a new condition table ex A922 in R/3 do we need to create a new adpater object ZDNL_COND_A922 or we can download using the adpater object DNL_CUST_CNDALL.
    All the condition types i mean Zxx which are created in R/3 how are they transferred to CRM .Are they transferred using the adapter object or they need to be created manaully in CRM system
    Thanks in Advance
    Regards,
    Krishna

    Hi,
    Every condition customising including conditioin types and condition tables are downloaded into CRM from R/3 using Adapter object DNL_CUST_CNDALL.
    But, the condition tables downloaded like this will be empty. This means they wont haev any condition record.
    In order to bring condition records too, you need to create an Adapter object.
    If the condition table is a standard condition table (say A340), then a standard Adapter object exists with name DNL_COND_A340.
    If its a manually created condition table say A922, then you have to create an adapter object ZDNL_COND_A922. This can be created by copying any standard ada[pter object adn modify it accordingly...
    Now jsut download this adapter object and it will bring all your condition records for the condition table.
    Kindly reward with points in case helpful.....
    Sharif

  • PRICING DETERMINATION WITHOUT CONDITION RECORD

    HI ALL,
    can anybody explain me when you creating one purchase order if there no condition record for this material (for an example info record) how the price can automatically picked up and sit into the net price field.
    What is big-pricing procedure (RM0000)?.
    PLEASE EXPLAIN ME IN DETAILS WITH A PROPER EXAMPLE.

    Hi
    There is a condition type P101 to adopt the price from the Material master. Apart from this the Price is determined based on the info update indicator, this will creat an info recoprd automatically, if you see the inforecord then the price will not be present as this info record has not been manully created.
    RM0000 is the Standard Pricing procedure given by SAP.
    Determination of Purchase Price (Example)
    Purchasing creates a PO for 100 swivel chairs at $250 each, to be supplied by vendor Miller Co. No outline purchase agreement exists with this vendor. The agreed condition (discount of $10 granted on each chair purchased) is stored in an info record. No general price stipulations apply.
    The system carries out the following price determination process:
    Assignment of price calculation schema:
    RM0000
    Search for condition records belonging to the condition types listed in the calculation schema:
    The system searches only for condition records belonging to condition types that are marked in the schema as non-manual.
    Condition type PB00
    Determination of access sequence
    0002
    Accesses within access sequence 0002
    Accessing of condition table 068 (plant-specific agreement item) is not carried out
    Accessing of 016 (contract item) is not carried out.
    Table 017 (info record) is accessed and the condition record is found.
    Condition records belonging to the other condition types are then sought.
    In the example, no further condition records are found because condition type RB00 (discount) is a supplementary condition belonging to condition type PB00 and thus has no access sequence of its own.
    The system then suggests a price of $240 per chair in the purchase order. The buyer can then enter further conditions (covering delivery costs, for example).
    Hope this clears your doubts.
    Please go through the link for more details
    http://help.sap.com/saphelp_erp2004/helpdata/EN/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Thanks & Regards
    Kishore

  • How to transfer the transactional dat a using ale

    hi to all abap gurus
    i heard that we can transfer the transactional data ( like so data , po data ) using message control technique by ale technology . . can u please give  all steps  in message control technique with one exapmle . i searched in the forum but i did not get answer . pls points will be rewrared for good answers.  if u want to give links pls give exact links .

    Hi ,
           here is the configuration.
    MESSAGE CONTROL (USING EDI / ALE)
    For Purchase order (Message control using EDI and message type ORDERS) – STEPS
    Settings to be done in the Sending system
    From NACE
    Choose Application – EF ( Purchase order), press on condition record
    Output type – NEU – Purchase order / double click ;choose  Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11) execute. Key in the data (vendor –vendor11, name – name1, partner function  - VN, Partner – Vendor11,Medium – 6 (EDI), time – 4(send immediately), language – EN).
    Press on output types , choose NEU –Purchase order, double click,  Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time – send immediately, Transmission medium – EDI, Partner function –VN)
    Create RFC destination from SM59 (ZNARA_ALE_EDI).
    Create a port from ZNARA_ALE.
    Create partner profile vendor11 under LI and not LS. PARTNER NUMBER SHOULD BE  SAME AS THAT OF VENDOR SET IN THE CONDITION TYPE.
    In the outbond parameters of the partner profile Vendor11 key in the data (Reciever port -> ZNARA_ALE,
    Basic type –ORDERS05, Message type – ORDERS ) Go to the message control and key in the data (Application – EF, Message type – NEU, Process code –ME10, Transfer immediately )
    Create a purchase order from ME21 with data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11). System will generate an outbond Idoc automatically which can be seen from WE02.
    For Purchase order (Message control using ALE and Message type ORDERS) - STEPS
    To transfer the idoc from Client 555 to 500
    Settings do be done in 555.
    From NACE
    Choose Application – EF – Purchase order, press on condition record
    Output type – NEU – Purchase order / double click ;choose  Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11) execute. Key in the data (vendor –vendor11, name – name1, partner function  - VN, Partner – Vendor11,Medium – A (ALE), time – 4(send immediately), language – EN).
    Press on output types , choose NEU –Purchase order, double click,  Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time – send immediately, Transmission medium – ALE, Partner function –VN)
    From SALE create two logical systems and assign them to the respective clients (ZALERECV_N – 500, ZALESEND_N – 555).
    From SM59 create RFC destination with the same name as that of the receiving logical system  (ZALERECV_N).
    From BD 64(distribution model),  create a model view with Technical name ZNARA_PO (message type – ORDERS, Sender – ZALESEND_N, Receiver – ZALERECV_N). Generate partner profiles. Distribute.
    Note that partner profile will be generated under LS.
    Settings do be done in 500.
    From NACE create two logical systems and assign them to the respective clients (ZALERECV_N – 500, ZALESEND_N – 555).
    From BD 64(distribution model), keep the cursor on Technical name ZNARA_PO. Generate partner profiles. Note that partner profile will be generated under LS. Change the process code to ORDE in the inbond parameters .
    Now in client 555, Create a purchase order from ME21 with data (Purchasing doc type – NB, Purc organisation – 0001, Venor – vendor11). System will generate an outbond Idoc automatically which can be seen from WE02. The purchase order details will be updated in 555 thru the inbond idoc.
    IMP data for message control in  Sales order creation.
    Partner profile to be created under KU.
    Outbond parameters in the partner profile (Message type – ORDRSP, Basic type – ORDERS02, partner profile - SP) In Message control (Application – V1, Message type – BA00, Process code – SD10)
    Notes:
    Check the entries in the NAST table to see whether outbond idoc has been created successfully or not
    If you have choosen collect idocs in the partner profile, use trans code BD87 to process them
    Table EDP13 - Partner Profile: Outbound (technical parameters)
    Table EDP21 - Partner Profile: Inbond (technical parameters)
    Please reward if useful.

Maybe you are looking for