ALE Distribution for custom HR infotypes.

Hi All,
We have a scenario where we have to distibute custom infotypes. Here is the process i am following.
Create Infotype 9004.
Created segment type Z1P9004 with all the fields in infotype 9004.
Attached Z1P9004 to custom infotype 9004 in table T777D.
Exteded the basic type ZHRMD_A and added the segment Z1P9004.
In we20 for partner profile HRMD_A, specified the extension ZHRMD_A.
Now, when i run PFAL, all other standard infotypes are getting populated and idoc getting created success fully. But even after entering records for 9004 infotype, i could not see it in my idoc.
I know i may be missing things for doing this. I have searched help.sap.com and sdn.sap.com .... but could not find any precise documentation.
Last but not least....I am bit new to this HRMD_A.
I would really appriciate if some one can guid me on this.
Thanks very much in advance.
Krishna M

I have used exit EXIT_SAPLRHA0_004.
IF f_idoc_control-mestyp = 'HRMD_A'.
f_idoc_control-cimtyp = 'ZHRMD_A'.
ENDIF.
This will take care of every thing, i dont even need to populate/fill any segments, every thing is taken care by SAP.
The above change makes the custom segment as if another standard segment.
Thanks for all the replys...
Best Regards,
Krishna M.

Similar Messages

Change Pointers activation for customer specific Infotype

dear friends,
could you please let me know how to activate the change pointers for customer specific infotypes? Currently we are using message type HRMD_ABA.
regards,
jp

Anand:
Unfurtunatly, not all the modification are registered in the log. For ei., You can track the systema status modification, the PR generation, etc. What fields change are you trying to modify?
Hope this help
Ezequiel

ALE: how do I use dependent distribution for customer and vendor addresses?

Hello SDN'ers
Hopefully someone can help me with an ALE question.
We have two ERP systems connected with ERP - Retail and AFS.
Customers and Vendors may be created in Retail, and are distributed to AFS using DEBMAS, CREMAS and ADRMAS messages.
Not all customers and vendors are required in AFS, so we have various filters set up in the Retail distribution model (BD64).
However with the filters in place, addresses were still being distributed for customers and vendors that had been filtered out.
To try and avoid this for vendors, we created a filter group for AddressOrg.SaveReplica in receiver determination. In the filter group we selected Dependent Distribution for CREMAS (Address owner object).
This works perfectly for vendors - vendor addresses are now only distributed if the vendor itself is distributed.
However I've now discovered it is preventing any customer addresses from being sent! I was surprised about this: I expected CREMAS dependency to only affect vendor addresses. Can someone tell me:
- is this how dependent distribution is designed to work? In which case can anyone offer any suffestions to achieve the filtering some other way?
- or are we doing something wrong to be getting this result?
Thanks for any help!
regards, Roger

Hi all,
as Robert suggested, I've written an exit to get round this, although I'm surprised I should need to!
What I did was to code an enhancement in function group BDBF, at the start of subroutine COMPUTE_LOGIC_EXPRESSION.
* In the case of addresses, dependencies should only be applied for the appropriate type of address
data: lwa_tbd14 type tbd14.
if P_MODEL_DATA-FTYPE = C_FTYPE_DEPENDENCY_FROM_MESTYP.
*   Dependency from Message Type.
*   Read the Address Object type
    READ TABLE P_FILTER_VALUES
                     WITH KEY OBJTYPE = 'AD_OBJTYPE'
                     BINARY SEARCH.
    if sy-subrc = 0.
*     Check if the Message Type is linked to the Address Owner Object Type
*     (Table is buffered on DB)
      select single *
        from TBD14
        into lwa_tbd14
       where MESTYP = P_MODEL_DATA-FMESTYP
         and OBJTYP = P_FILTER_VALUES-OBJVALUE.
      if sy-subrc <> 0.
*       Wrong type of address for this dependency - stop here
        P_REPLICATE = c_true.
        exit.
      else.
*       Correct address type. Standard processing continues, checking any
*       filter values set up against the Address Owner Object Type.
      endif.
    else.
*     It isn't an address - continue with standard processing
    endif.
endif.
Let me know if this helps you, or if you know of a better way to achieve the same result.
Roger

ALE Distribution for Message Type FIDCC2

Dear all,
I would like to confirm my steps below in setting up the ALE distribution of message type FIDCC2, to ensure that I did not do anyhting that impact other company code that already live in the system :-
1. Use tcode OB87 to add the Global Company Code, XBJ01.
2. Use tcode OBV7 to link a dummy (non-existence in sending system)
Chart of Account to the Global Company code XBJ01.
3. Use tcode OBB5 to assign the Global Company Code, XBJ01, setup in step 1. to the an existing company code BJ01.
4. Use tcode BD64 to setup a distribution with message type FIDCC2, and
filter with value XBJ01.
5. Create an FI document using tcode FB01 with company code BJ01.
6. IDOC is created successfully with message type FIDCC2.
Is there above steps correct? As there are times I receive an error message when trying to do a PGI with company code other than BJ01 "F1302 No cross-system company code is defined for company code TR01".
Another question is, with setting up of FIDCC2 with ALE distribution, any transaction in SAP that will generate a FI document will have IDOC created, right?
Thank you.
Best Regards
Chee Hean

I don't know if you still have this problem but my team and I faced a similar issue in production. Due to a project we're handling, a tool that we are executing requested us to create a Distribution Model based on FIDCC2. This stuck hundreds of thousands of FI Document. Actually, for any FI document the system generated an FIDCC2 and it's not possible to reuse those IDocs because the FIDCC2 Message Type has a structure completely different from FIDCMT (the original message that the system should generate). We identified all the IDoc that should be generated and re-create the Idocs in the target system and the Idocs we posted correctly. We change the FIDCC2 IDocs status to 62 or 32 (depending if inbound system or outbound system). I recommend to investigate about this message type before use it. This Message Type is stronger than any other message type so it must be filter perfectly otherwise, for sure, problems will appear.
Regards,
Hugo

Regarding ALE-iDoc for Customer Master, J1ID and FD32

Hello all
Scenario:
As per client's requirement we have to develop idoc so that followings requirements will meet:
Say there are two servers a) MDM Server b) PRD Server
1] As and when I'll create customer master data in MDM server then customer master should get created with that data in PRD server
which I can achieve through BD12 by doing some idoc enhancements
2] Simillarly when i'll create data using transaction J1ID and FD32 in MDM Server (Data relevant to customer master) then that data also should get created in PRD server using Idoc
May I know which
1)message type we can use (as we use DEBMAS in case of Customer Master) for J1ID and FD32
2) Any transaction to send data from one server to another server for transaction J1ID and FD32 (as we use BD12 in case of Customer master for sending data created using transaction XD01)
Thanks,
Mahesh

Hello Mahesh,
In the case of customer master it would be better if you would use standard message types and t code to transfer ddata.
But in the case J1ID and FD32 you can build a standalone idoc
Follow these steps to build custom message types and futher transactions
WE81 - Create message type
WE31 - Create segment
WE30 - Create Idoc type
SALE - Define Logical system (not required if already exists)
SM59 - Define RFC (not required if already exists)
WE21 - Define ports (both in sender and receiver)
WE20 - Define Partner profile (both in sender and receiver)
BD46 - Distribue the model view.
SE38 - Create a program to send the idoc in the sender sytem.
SE37 - Build inbound function module to receive the idoc for receiver system
WE57 - Assign FM to message type
BD51 - to change the characteristics for inbound FM
WE42 - Create Inbound process code.
Hope this would help you.
Thanks and Regards,
Ranjith Nambiar

ALE Distribution for alternate BOM environment

Currently the ALE framework does not support distribution of alternate BOMS between SAP r/3 systems. Does anyone know if there is a workaround for this issue?
Please provide any input.
Thanks.

Hi Stacey,
Have you looked this program <b>RBDSEBOM</b> or t/code <b>BD30</b> for alternate BOM distribution?
Hope this will help.
Regards,
Ferry Lianto

FB, BAPI for custom PD Infotype

Hi there,
i am looking for an FB or Bapi to read the Data of my own createt Infotyp. Can anyone Help btw. it is a PD Infotype!
Thanks in advance
Mathias

Hi
try this....
RHPP_Q_PROFILE_READ
hope this will work
Anuj

ALE Distribution Lock

Hi all,
can anybody tell me what is ALE Distribution Lock ...
regards
sreedhar rusuma

Here is the documentation for ALE distribution lock
You determine whether you want an object, for example, a document, to be distributed via ALE into other systems by setting the status, for example, document status.
The indicator Distribution lock prevents an object, for example, a document, from being transported into an ALE system.
A change pointer is always set for the distribution lock during distribution even when sending within the ID PDM Solution. The system automatically creates a change indicator and a Master IDoc for distribution when you change a distribution relevant field, for example, status, for a message type, such as DOCMAS for documents.
It is possible to ignore the distribution lock when you send objects manually. In this case, the entire object is transported into the ALE system according to the distribution model.
Manual distribution is only of importance for change master records within the ID PDM system.
See also:
Change Master Record : IDoc Type ECMMAS01
Objects
You can control the ALE distribution for the following objects within ID PDM via the status:
Material
Characteristic
Class
BOM (material BOM, document structure)
Document
Object dependencies
Change master record
Activities
You can process the status for the desired objects.
1. Select in Customizing Cross Applications Components --> Distribution (ALE) -->Standard ALE Business Processes --> Logistics --> Master Data Distribution --> Integrated Distributed PDM Solution (ID PDM) --> Object status (for example, Define BOM status).
2. Process the indicator Distribution lock

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

ALE/IDOC-How to create Change Pointers for Custom Infotype

Hi,
My requirement is to transfer custom OM infotype changes using IDOCs.
But its not creating any change pointers for that infotype.
The message used is a copy of standard message OM_HRMD_A.
Can any one please help me out in this issue.
Thanks,
Sarika

Hi Sarika,
How did you solve this issue? We are also facing a similar problem, it will be helpful if you could explain how you found out the solution.
Thanks
Anu.

Custom HRP Infotype for e-Recruiting

I am trying to create a custom HRP infotype to be used in our e-Recruiting system. I want to be able to update the infotype using the SAP standard RH_INSERT_INFTY and like function calls. However my entry in table t777d won't let me change the Update type to anything other than blank (No update via personnel planning update task). I also am having issues which I am not sure if this stems from that problem or not but when I try to use the RH_INSERT_INFTY I get a short dump when it tries to do an insert with a vtask of D because the data doesn't appear to be mapped to the correct fields. My input table type is of type p9xxx and it seems to be mapped correctly until the last stage when it actually tries to insert the line into the table. Any suggestions for what might be wrong? I have checked to make sure that the p9xxx and hrp9xxx have the same structure and they appear to match correctly

You could search/post this question in the HR forum...

Creation of subtypes for a custom PD Infotype.

HI Experts,
We are in the process of creating a custom PD infotype (say 9003 and hrp9003 is the table).
We want the infotype to have 2 subtypes (say 01 and 02).
We followed the steps and created the infotypes and also made sure that we create 2 subtypes and we were successful till here.
However, when we try to maintain data in IT9003(pp01), we never get an option to specify the subtype and hence whatever data we save doesnu2019t have any value in subtype field.
Please help up out to save data with subtypes.
We want something similar to infotype 1001, where we can select the relationship(subtype) and save accordingly.
How to make the subtype appear in the data creation screen? Do we have to do some changes in the module pool program?
Regards,
Ravikeerthi.

Check the tables V_778U.....assign your subtypes to custom PD Infotype.
Check the table for Your PD infotype and subtype assigned to Object Type..
SPRO --> OM --> Basic Settings -->Data Model Enhancement -->Infotype Maintenance
Mohan

Logical database PNP not retrieving data for custom infotypes.

Hi all,
I am using logical database PNP in a program. I have declared infotypes as follows:
INFOTYPES: 0001, 0002, 0041, 9801, 9840.
The problem is that the logical database is retrieving data for the standard infotypes but not for the custom infotypes. Any explanation as to why data for custom infotypes is not being retireved and how this can be solved will be greatly appreciated.
regards,
Hamza

solved

Error for custom infotype in PPOME

Hello Experts,
I have created one custom OM infotype for object position.Now when i am trying to acccess that Infotype in PO13 it is working fine but when i am trying to acccess the custom infotype in PPOME it is giving a dump.
EERROR:
Error in the ABAP program "SAPLRHOMDETAIL_PP01" had to be terminated because it has come accross a statement which cannot be exceuted.
An exception occurred.
The exception, which is assigned to class 'CX_SY_ASSIGn_CAST_UNKNOWN_TYPE', was not caught in procedure "INIT_SUBSCREEN" "(FORM)" nor was it propagagted by raising clause exception.
The reason for the exception is :
The type "" dynamically specified with ASSIGN....CASTING TYPE is unknown.
Please guide me where i am doing mistake.
Thanks in advance.
Shweta

Hi Sudha,
PM01 is the tcode.
Similar questions were already answered in the following threads
ABAP HR : Infotype Enhancement
So please search and then post specific queries.
rgds
gayathri

T code for custom infotype in PA

Hi
T code for custom infotype in PA.
Regards
Sudha

Hi Sudha,
PM01 is the tcode.
Similar questions were already answered in the following threads
ABAP HR : Infotype Enhancement
So please search and then post specific queries.
rgds
gayathri

ALE Distribution for custom HR infotypes.

Similar Messages

Maybe you are looking for