IDoc generation with Message Type HRMD_A with filter on Personnel Area

Hello All,
We are facing an issue in generating IDoc using the standard message type HRMD_A.
When we have no filters on the Distribution Model, the IDoc is generated through RBDMIDOC. When we use the filter on BUKRS, it generates the IDoc but gives an error status "Cross-system company code XXXX does not exist". I know to how resolve this issue. But, we tried to filter the changes with Personnel Area this time. So I have used the field PERS_AREA in BD59 with segment type E1PLOGI. When I run the standard report RBDMIDOC it gives the message "No data selected for distribution".
I have checked the field name PERS_AREA from table TBD10, and it is mapped to T500P-PERSA. Change pointers are triggered and stored in BDCP2. Request experts to suggest what could be wrong with this.
Thanks,
Anil

Hello Michele,
If you have added BUKRS in BD59 for the message type, you will see Company Code (not filter1) in your filter criterion in BD64.
Have you included the following code in FILTER_VALUES_SET method of the BADI implementation.
  CHECK OTYPE = 'P '.
  SELECT * FROM PA0001
           INTO PA0001 WHERE PERNR =  OBJID
                       AND   BEGDA <= SY-DATUM
                       AND   ENDDA >= SY-DATUM.
record is valid today, no authorization check
    EXIT.
  ENDSELECT.
  IF SY-SUBRC = 0.
    FILTER1 = PA0001-BUKRS.   ELSE.
    CLEAR FILTER1.
  ENDIF.
Lastly, just make sure the record you are testing for has your desired company code PGPB.
Regards,
Anil

Similar Messages

  • Idoc generation for message types

    Hi All,
    regarding IDOC generation....
    how do we activate the message type so that every time the application data which is created or changed or deleted generates the idoc and send it to other system. If iam not using Chnage pointers technique then i would not be activating the message type in BD50. In such  case ie if the message type is not present in BD50 list and if change pointers is not used to transfer that message type . How do we genrate the idoc for such message types.
    Thanks
    Avinash

    Hi,
    For ur scenario u need to go for change pointers method only.U have other options like distributing master data and transactional data..But i don't think anything otherthan change pointers is useful.
    Regards,
    Nagaraj

  • Problems with PROOF field in idoc (message type HRMD_A)

    Hello,
    I'm using the standard message type HRMD_A with IDOC base type HRMD_A06 and the function module IDOC_INPUT_HRMD.
    I have a doubt with field 'PROOF' when I fill the IDOC. Does anybody know for what is it used? For example, what's going to happen if I put PROOF = 'X' in an update operation?
    In my case I have tested that when PROOF = 'X', I receive the following warning in intotype 0001:
        The EMPLOYEE_ORG_ASSIGNMENT-ADMINISTRATOR_GROUP field is not maintainable in dialog, so it is ignored
        The EMPLOYEE_ORG_ASSIGNMENT-ORG_UNIT field is not maintainable in dialog, so it is ignored
        The EMPLOYEE_ORG_ASSIGNMENT-COSTCENTER field is not maintainable in dialog, so it is ignored
    but I cannot be sure if these warnings are due to PROFF.
    In the change data record screen, I have filled the following fields: plan version ('01'), object type ('P'), object id (employee number), PROOF ('X'), Operation ('U'). Structure for the idoc is EDIDC->E1PLOGI->E1PITYP.
    Any help on this?

    Hello,
    I'm using the standard message type HRMD_A with IDOC base type HRMD_A06 and the function module IDOC_INPUT_HRMD.
    I have a doubt with field 'PROOF' when I fill the IDOC. Does anybody know for what is it used? For example, what's going to happen if I put PROOF = 'X' in an update operation?
    In my case I have tested that when PROOF = 'X', I receive the following warning in intotype 0001:
        The EMPLOYEE_ORG_ASSIGNMENT-ADMINISTRATOR_GROUP field is not maintainable in dialog, so it is ignored
        The EMPLOYEE_ORG_ASSIGNMENT-ORG_UNIT field is not maintainable in dialog, so it is ignored
        The EMPLOYEE_ORG_ASSIGNMENT-COSTCENTER field is not maintainable in dialog, so it is ignored
    but I cannot be sure if these warnings are due to PROFF.
    In the change data record screen, I have filled the following fields: plan version ('01'), object type ('P'), object id (employee number), PROOF ('X'), Operation ('U'). Structure for the idoc is EDIDC->E1PLOGI->E1PITYP.
    Any help on this?

  • Creation of IDOC with message type INVOIC01

    Hi All,
    I am trying to create a new IDOC with message type INVOIC01.
    When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
    However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
    The client wants me to create IDOCs with basic type INVOIC01.
    Can anyone please help?
    Thanks in advance.
    regards
    Nagarajan

    Hi Nagaraj!
    I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
    Thank You,
    Natalija

  • RFC error "No authorization to send IDOCs with message type ..."

    Hi all,
    I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
    I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
    I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
    Any suggestions?
    Regards,
    Liesel

    Hi Liesel,
    The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
    Please check if the user id/Password that you have given has all the authorization.
    Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
    There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
    Regards,
    Abhy Thomas

  • Error : No authorization to send IDocs with message type MATMAS

    Hi All,
    My scenario is FILE-XI-IDOC.
    I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
    When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
    Do I need to give any authorizations on XI side or on R/3 side?
    If so, what is the authorization required?
    I could not find the note :837595.

    <i>You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
    This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
    Solution
    In transaction PFCG, extend the role of the logon user by adding the following authorizations:
    Authorization object S_RFC
          Field name RFC_TYPE value FUGR
          Field name RFC_NAME value EDIMEXT, SDTX
          Field name ACTVT    value 16
    Authorization object S_IDOCDEFT
          Field name ACTVT  value 03
          Field name EDI_CIM value ' '
          Field name EDI_DOC value TXTRAW01
          Field name EDI_TCD value WE30
    Authorization object S_CTS_ADMI
          Field name CTS_ADMFCT  value TABL
    Authorization object S_TABU_DIS
          Field name ACTVT      value 03
          Field name DICBERCLS  value</i>
    from the note mentioned above.
    Regards
    Bhavesh

  • Workflow Ends in Error " No auth to send IDocs with message type ORDRSP"

    Hello All,
    I have created an RFC user with limited Authoprizations including WE* tciodes and a few ME* transactons for an ALE Set up. I want to make sure i would not be giving more authorizations (extensive) to this RFC user and assign Just required authorizations. So i started testing testing and the inbound IDOC ended in error with a message " No auth to send IDocs with message type ORDRSP" Message no. SR053. Is there any way to find out what is the missing authorization object for the User. Any inputs would be really apprecaited.
    Br,
    Sri

    Hi !
    Becaus alle this happens in beckgound, things are a bit difficult but solvable....
    What you should do is a "Authority trace" ... as follows....:
      - Go to the ST01
      - Mark "Authorisation Check"
      - Swich the trace on for your Workflow user
      - Execute the Workflow until the error uccurs
      - Go back to the ST01
      - Press the "Analyze" button and see what error occurs
    Dont forget to swicht the trace off... otherwise the tracefiles become realle BIG !
    Regards
    rainer
    Some Reward poins would be nice if that helped....

  • Issue: "No Authorization to send Idocs with message type Orders" - IDX5

    Hi All,
       I am working on a File to IDoc(Orders.Orders05) scenario. The sender is PI Server and the receiver is the SAP ISR system. A technical system has been created in PI SLD for the ISR system and a Business system is added to that. The logical system created in ISR system using Tcode BD54 is added to the business system in PI. A new RFC destination is created in PI system to connect to the ISR system.
      On the ISR system Partner profile is created using TCode we20 with the same logical system name already created using Tcode BD54.
    When sxi_monitor is executed on the PI system, It shows checked flag on the Inbound side and Red flag on the Outbound side. And when idx5 is executed, it shows the new Idoc number and when it is double clicked, it shows the Status Text as
    "No Authorization to send IDocs with message type Orders".
    All authorizations have been provided on the Sender side.
    Please let me know if any authorization need to be provided on the ISR system or Is this an error on any settings.
    Thanks in Advance.
    Stalin S.

    Hi,
    Check this Thread which deals with the Authorization Issue
    RFC Adapter
    And also check this how to check whether u have sufficient authorization to send the Idocs or not
    To test the Authorization check
    Double click the RFC Destination that u have created in XI towards R/3 in SM59
    Select UtilitiesTestAuthorization test
    By this you can come to know whether your user is having the propper authorization or not
    REgards
    Seshagiri

  • Outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON

    Hi Friends
    I am trying to pack outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON.
    But IDOC has error Specification of destination HU missing.
    Could you please help us to resolve the issue to Pack the outbound delivery with the  IDOC.
    Thanks
    SR

    HI Ian Kehoe
    Sorry for delay in reply
    Thanks you very much
    I solved that problem .
    Could you please advice  test data for IDOC  DELVRY06 packing hierarchy (multi level packing) to pack SAP outbound delivery.
    Thanks
    Ravi

  • No authorization to send IDocs with message type R

    I'm in the process of installing some business content for a 3.5 prototype.  When trying to load some master data I get the following error in the transactional RFC in the source system.
    "No authorization to send IDocs with message type R"
    Any clues to what may be causing this?
    Any help appreciated.
    thanks
    Mike

    Hi Michael,
    the suggestion for SAP_ALL was just for testing purposes in order to see whether it works then. If security is an issue you should reduce the authorization to the ones really needed (see note).
    Another security option is to make the background user a system user and not a dialog user.
    Regards, Klaus

  • ZHRMD_A Custome message type issue with custom segments.

    Hi Experts,
    We have implemented ALE in HR system, we have all other ALE using HRMD_A and we have jobs scheduled for HRMD_A message type. We dont want this job should trigger our model and distribute the data. So we have reduced the HRMD_A messae type to ZHRMD_A for basic type HRMD_A06. Every thing fine. After upgrade of SAP FROM ECC6.O to EHP4, PFAL is not creating IDOC segements for custom segments Z*. for example Z1P0002....ETC, though there is personal data for PERNR.
    Please guid if you have come across such situation and solution.
    Thanks & Regards.
    Venkat.

    Hi Venkat,
    In the same way i too have one situation like...have different model view with same message types( and same extension type) for various countries from one sender system.
    Should i create reduced message type for each model view?
    Or can i use same message type HRMD_A for various model views?
    If i can use same message type and same extension type for various model views is there any restriction we need to write in USER EXIT  EXIT_SAPLRHA0_004?
    Regards,
    Lava.

  • Message Type - STTPOD with Process Code as - OPOD

    Dear All,
    I am using Standard Message Type - STTPOD with Process Code as - OPOD and Basic Type as - DELVRY03
    I am creating a New "Z" Segment Copy of "E1EDL20"
    I want to Add in one FIELD
    EKPO - ELIKZ which is Delivery Complete INDICATOR
    How can i fetch data when the IDOC is generated and to take the value from this FIELD.
    Is there any Userexit or BADI
    This we are doing so as we can pass message to SNC for GR Done and Completed
    Regards
    Amey Kulkarni

    Hi Amey,
    As you are using Standard Message Type - STTPOD with Process Code as - OPOD and Basic Type as - DELVRY03
    There is no need create Z-field or any implementation of Userexit or BADI for GR updation in SNC.
    In SNC for updating PO GR status you need to maintain below validation settings:
    TCode:SPRO>Supply Network Collaboration>Basic Settings>Validation>Own Settings-->Maintain Settings in Validation Profiles
    Validation profile=POC1
    Validation check=PO_OPENQUAN_FROM_ASNGRQUAN
    Check status=Inactive
    Validation profile=POC1
    Validation check=PO_OPENQUAN_FROM_ASNQUAN Inactive
    Check status=Inactive
    Validation profile=POC1
    Validation check=PO_OPENQUAN_FROM_POGRQUAN
    Check status=Active
    save the setting.
    Regards,
    Niikhil

  • Issue with Message Type Triggering during Inbound Delivery Creation

    Hi Experts,
    Hi Experts, 
    Currently we are facing issue with message type triggering during inbound delivery creation:
    In NACE transaction for Inbound delivery we have 3 custom output types:
    Pricing Procedure Used is standard one -> E10001
    Z140  Inbound Delivery Create  (This should get triggered when IB delivery is created)
    Z141  Inbound Delivery Change (This should get triggered when IB Delivery is changed)
    Z142  Inbound Delivery Delete(This should get triggered when IB Delivery is deleted).
    At present if i check delivery in  VL33 -> Extras -> Delivery Output
    Both  Z140 and Z141 are being triggered during IB delivery creation. While it should be only Z140.
    Could you please suggest that are we missing any configuration in SPRO or we need to create any custom routine (requirement) to handle this?
    Thanks

    Hi,
    There is no fine-tuned control for inbound delivery messages as for Purchase order. Hence I guess to meet your above requirement, you have to go for a custom solution similar to the PO fine tune control settings.
    Thanks,

  • Filter Infotypes based on Company Code for the Message Type HRMD_A

    Hi,
    I have a requirement to send different infotypes for different Company codes using the same distribution model for the message type HRMD_A.
    Example :
    For the BUKRS 2500 I need to send infotype 0000 ,0002,0006
    For the BUKRS 2600 I need to send infotype 0000 ,0008,0009
    It will be a great help for me if any one can guide me on that.
    Regards,
    Raka

    Hi ,
    Thanks for the reply.
    I alredy have done that . But its not working.
    Its working only for infotype 0001.
    If the infotype is there in any of the filter groups, the data will be sent irrespective of the Com Code.
    Regards,
    Raka

  • Message Type HRMD_A or HRMD_B or HRMD_ABA

    Hi,                                                                               
    We have a requirement to update HR Master Data into our SAP System from 
    an External System via Middleware (TIBCO in this case)                                                                               
    Our SAP System details are as follows: -                                
    ERP 6.00, HR 6.00, WebAS 701                                                                               
    By Updating Master Data into the system we mean: -                      
    1) Update existing PA and PD InfoType records                           
    2) Insert new PA and PD Infotype records                                
    3) Update data into Custom Infotypes / Custom fields in standard        
    infotypes                                                                               
    I have read quite a few SAP Notes and Support Messages (Application Area
    BC-BMT-OM-ALE and others) and even the Documentation in SALE           
    transaction, but I am not fully convinced which one to use for my       
    requirement                                                                               
    Here's my observation on these message types: -                                                                               
    HRMD_A   > is quite exhaustive (has maximum number of infotypes) and SAP
    recommends to use this for SAP HR to SAP HR distribution                                                                               
    HRMD_B   > Support Message 1082157_2005 says to use this for External   
    System Transfers which is what I need but has only a few PD infotypes   
    and nothing else (I would not like this either)                                                                               
    HRMD_ABA   > Contains limited number of PA and PD infotypes e.g. some   
    very basic infotypes like 0027 are not present. Also SAP recommends this
    to use for SAP HR to SAP system without HR components such as CRM, EBP,
    etc.                                                                               
    But the Documentation in SALE appears speaks something different. It    
    says                                                                               
    HRMD_B   > Distribution from SAP HR to an SAP Basis System. This is     
    quite different from what is mentioned in message 1082157_2005 which    
    says it can be used for legacy data transfer                            
    So what would be the right message type for...                         
    A) Inbound HR Master Data / Org. Dataposting                           
    B) Outbound Master Data / Org. Data distribution from SAP                                                                               
    especially when a non-SAP system is involved                                                                               
    Please note that the Idoc must be flexible and support updates into any
    PA-PD infotypes (through Idoc extensions and BADI/customer exit        
    implementations if needed which is fine with me)                                                                               
    Thanking You in advance        
    Regards,
    Aditya

    Hi,
    The message types used for HR are:
    HRMD_B: transfer data from legacy systems, non SAP system. (E.g. People Soft).
    HRMD_A: transfer data between 2 HR systems.
    HRMD_ABA: transfer data from an HR system to a #non-HR# system (CRM, SRM, etc..)
    You should use message type HRMD_B to transfer data from HR system to external system (Northgate Arinso) but it has only a few PD infotypes and nothing else.
    Hope it helps,
    Regards
    Christine

Maybe you are looking for

  • Can't enable iPod hard disk

    I am trying to enable my 30GB iPod to be used as a hard disk to save documents. When I initially plug my iPod into my Mac, the iPod icon appears briefly on the desktop, then disappears. Then, when I try to select "Enable Disk Use" on the iPod Summary

  • Setting Portlet Properties in Development

    I am trying out the Portal 9.2 Trial, so am very new to this. I have created a very simple JSP Portlet in Workshop and created a "Message" Preference for this Portlet with a default value of "Hello World". I have created an instance of this Portlet i

  • Changing File Associations

    I associated the file type "ASPX" with Mozilla Firefox and accidentally checked "always launch Firefox" for this file type. As a result, whenever I load an ASPX page, Firefox opens a new window and seems to get in a recursive loop, opening window aft

  • Apple news mails in wrong language

    For a while I keep receiving mails from [email protected] in dutch whereas my appled Id preferences indicate english as communication language. How / where do I have to set up the language for these mails ?

  • Problem extracting data from XML

    The XML file format is: <xml> <condesa> <lote> <loteid>H50601</loteid> <nombre>Servicios</nombre> <categoria>Escuela</categoria> <subcategoria>Arabe</subcategoria> <telefono> 55532255</telefono> <direccion> Juan pedro 23</direccion> <image>roble.jpg<