[HR] About message type HRSM_D

Hi to all
As a migration issue I was asked to migrate personnel absence records (infotype 2001) data from an SAP 4.6 legacy system to an ECC5 system. Actually, I have no PT knowledge but I want to use HRSM_D message type to transfer data through LSMW. Does anyone know any FM or report filling this IDoc structure like "RH_OBJECT_IDOCDATA_CREATE" does for HRMD_A?
I would welcome any other ideas for migrating 2001 data through LSMW as well.
Thanks

Hi Suresh
Thank you for the answer. The BAPI you've mentioned belongs to BO 'ABSENCE' and it has no ALE message type in standard. I do not want to genarate, either. Besides, it is obsolete as of Release 4.6A. However, it may be replaced by BO BUS7007.
Actually, what I want is an outbound FM handling the HRSM_D message type.
There are more than one legacy system and this way is prefered by the client.
Thanks

Similar Messages

About Message Types

Hi friends
Differentiate between ABEND and ERROR messages please.
Thanks
Suren

Hi,
Please refer below:
E Message (Error)
When the system detects an error, E messages should be used. Incorrectly completed fields must be ready for input. If consequential errors occur, we recommend to make not only the incorrectly filled field ready for input but also those fields whose entries have contributed to the error.
Depending on whether the E message was issued by a primary window or a dialog box, it is either displayed in the Status Bar of the primary window or in a separate dialog box.
A Message (Abend)
A messages are intrinsically of a modal character, that is, a separate dialog is inserted into the current task. Therefore, they are displayed in modal dialog boxes
A messages do not allow the user to make any further entries. The user can only acknowledge the message. The task is abruptly terminated and the system returns to a higher-level menu.
A messages should only be issued in extraordinary circumstances, for example, when a system-related error occurs or if the error can no longer be handled by the task. In all error situations handled by the task, however, it should be possible for the user to remain in his work environment. A messages should therefore be avoided, if possible.
Thanks,
Sriram Ponna.

What's the purpose of message type ADRMAS

Hello,
I want to distribute customer master data using message type DEBMAS. I read something about message type ADRMAS. Why should I also use type ADRMAS because DEBMAS already contains address data?
Regards, Jan

Hi,
you may look to notes [384462|https://service.sap.com/sap/support/notes/384462] and [306275|https://service.sap.com/sap/support/notes/306275].
In short.
Business Address Services (BAS) has defined a central point for handling and storing adress data.
Starting with ERP release 4.5B, customer/vendor master data has integrated the BAS functionality in order to provide a consolidated handling of address data instead of a specific handling.
As a result, KNA1, KNVK still contain address data for historical and compatibility reasons BUT the real accurate address handling is within BAS tables.
The second consequence is that the address is now distributed with its own idoc types : ADRMAS, ADR2MAS, ADR3MAS.
So for accuracy reasons, you should distribute ADRMAS AND DEBMAS.
Hope this helps
BR
Alain

Message types?

hi am new to BI
pls help me to know about message types.
plese provide docs or pdfs if u have and that would be really helpful
thank u

Hi Ranjith,
Message Types:
A --> Termination Message
The message appears in a dialog box, and the program terminates. When the user has confirmed the message, control returns to the next-highest area menu.
E --> Error Message
Depending on the program context, an error dialog appears or the program terminates.
I --> Information
The message appears in a dialog box. Once the user has confirmed the message, the program continues immediately after the MESSAGE statement.
S --> Status Message and Sucess message
The program continues normally after the MESSAGE statement, and the message is displayed in the status bar of the next screen.
W --> Warning
Depending on the program context, an error dialog appears or the program terminates.
X --> Exit
No message is displayed, and the program terminates with a short dump. Program terminations with a short dump normally only occur when a runtime error occurs. Message type X allows you to force a program termination. The short dump contains the message ID.
For more info:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
Regards,
KK.

Resources for designing data types and message types

Hi
I wanted to know if anyone can recommend me some good resources which can explain the design considerations for designing data types and message types in XI which can help promote reusability.
Thanks.
Best Regards,
Kiran

hi,
there no rare rule whe you define your data type, why i tell you this, because you define a data type since the documentation that sender sistem team gives to you. so you only have to copy this structure to PI.
now about Message Type less problems, because, you a Data type is assign to a Message Type, whats it means.
when you define a DATA type you are defining the structure of you XML, que you assing the data type to a message type this structure pass to be an xml document.
Thanks you
Rodrigo

About the elusive message type 210.

Hi all,
Does anybody have ANY Document on message type 210 FrghtDet This is an Ansi X12 message but I can not find any details on the Internet at all.. Searching FrghtDet in Google gives no results.. Is there no website for FMDs and ANSI x12 at all??
Also I wanted some good resource in EDIFACT standards but right now I really want to find the full details of 210.
Thanks everybody,
Charles.

Hi Charles,
EDI 210 Messages are used to transmit Freight Charges (Officially "Motor Carrier Freight Details and Invoice").
We created an INVOIC IDOC to post these charges by mapping the necessary fields, and equating the SCAC codes to freight conditions that had been configured on the POs.
In our case, we could get 1 Freight Bill (EDI 210) covering several POs, so we created separate INVOIC IDOCs for each PO referenced on the Freight Invoice. actually, we allocate charges to each line item on each PO, but it is on INVOIC IDOC.
If you Google "EDI 210" you can find many examples of implementation guides. I suggest you start studying one of a partner that you are currently doing business with.
CN's is available www.cn.ca/PDF/EDI_210_Guide.pdf and is an example of all the fields and contains an example document as well.
Good luck!
Edited by: Jereme Chapman on Aug 7, 2008 5:48 PM

Message interface with two types of message types

Hi experts,
I am having problem that a proxy cannot be generated because of the (mixed) types of the message types that the interface is using.
The first message type is defined in the repository and another is defined as an external definition, imported in from an outside source.
Here is the SAP message I received when I tried to generate the proxy for this interface.
+++++++++++++++++++++++++++++++++++++++++++++
Interface uses external and internal message definitions
Message no. SPRX122
Diagnosis
In a message interface you can use messages from different sources:
1. Message types and fault message types edited in the Integration Repository
2. Messages imported into the Integration Repository (external definitions, RFC, IDoc)
In the current message interface, message types from different sources have been used.
Since messages from these different sources must be handled differently during proxy generation, such a mixture of messages within a message interface is not possible.
System Response
The interface cannot be generated.
Procedure
Change the interface definition accordingly in the Integration Repository.
++++++++++++++++++++++++++++++++++++++++++
The imported xsd is quite large and also contain many large includes. I don't have the option of creating the message type manually.
Any suggestions?
Thank you,
-michelle

Hi all,
I tried several things and the problem is still not resolved. This is what I learned.
First of all, I believed the SAP message about mixing of internal and external message is misleading or even wrong. I tried with both message types being external but I still get the same message that the interface has one internal and the other external message type.
Secondly, since Arvind suggested that I might have used an xml element that is not currently supported by ABAP proxy, I then change to another definition with the most simplest elements. I then attached this other definition to the interface and tried generating the proxy again. I still get the same system message that I am using mixing of message types in one interface.
My conclusion is XI still is not capable of generating ABAP proxy from external definition.
Does anyone have any comments/suggestion/experience on this issue?
Best regards,
-michelle

Custom - Material Master Update using an IDOC (Message Type - MATMAS_BAPI)

Hello everyone,
I was writing a functional specs. Basically, I want to update the material master MM02 using an IDOC (MATMAS_BAPI01 - Basic Type & MATMAS_BAPI - Message Type). This is currently working.
To my understanding, this currently uses function module - BAPI_IDOC_INPUT1 to update the material master after the IDOC is posted to SAP ECC from XI system.
Now I want to add one small validation logic before it actually updates the material master (MM02).
I looked around and found one exit - EXIT_SAPLMV02_002 in enhancement MGV00001. I was almost sure that this EXIT can be used to write the custom validation code before, actual MM02 updation.
However while trying to establish a link between this EXIT and BAPI_IDOC_INPUT1, I found that EXIT_SAPLMV02_002 is actually a part of another function module - IDOC_INPUT_MATMAS01 and not BAPI_IDOC_INPUT1. I am stuck here if adding the custom logic in the exit really going to work.
a bit of googling and I found from WE30 that the purpose of both these function modules are actually different. While BAPI_IDOC_INPUT1 actually create & updates the material master (also plant specific master data which is my need), IDOC_INPUT_MATMAS01 is just for maintenence of few fields in MM02 (may be custom fields).
Can anyone point out if my thing is in right direction?
Also please offer any solution where shall I put the Custom Logic in the EXIT or the some variants of
BAPI_IDOC_INPUT1.
A less technical explanation would be appreciated as I come from a functional background and invloved in this for writing the func specs. I want to make it sure that what I write is not useless and makes some sense.
Thanks in advance,
Arunesh

Hi Lalit,
Did some head breaking with the function module - BAPI_IDOC_INPUT1 to check whether it is calling the EXIT_SAPLMV02_002 internally. Couldn't get anywhere.
On question of another EXIT in BAPI_IDOC_INPUT1, I don't see any. I am not very proficient in ABAP code, I must say though.
I found the list of exits from google, almost same list everywhere.
http://www.sapfans.com/forums/viewtopic.php?f=21&t=296637
here I got the EXIT, I am talking about.
Any other way to find either the EXIT or link the above?
-- Arunesh

Partner profile,Message type

First time if I am configuring SAP R3 and SAP BW system
I need to create Partner profile and Port definition ,message type RSINFO,RSSEND,RSRQST.
Creating SAP R/3 source system in BW-I need to use RFC user or my user id is fine.
Any one help me out which message type goes to where or related any documents.
Please advise on this

Hi,
For info about source system connections see the following notes:
793717 Client copy into the BW client in Netweaver/mySAP ERP
606757 Naming conventions for logical systems
524554 Storing destinations in the BW environment 
423184 ALE: Problems with logical system names
325470 Activities after client copy in BW source systems
184971 Notes on BW source system connections 
184754 Procedure after BW database copy
184447 Building a BW-system landscape
184322 Procedure after DB copy of BW source systems
121163 BDLS: Converting logical system names
Kind regards, Patrick Rieken.

Message type, Idoc type and process code in ALE/Idoc

Each Idoc version(creams01 or cremas03) will have seperate process codes in Inbound process?
Whether Message type triggers the process code or the Idoctype/idoc triggers the process code in Inbound process?
regards
Message was edited by: henry

Hi Henry,
About your question as how should you assign seperate process code for the same message type ( with different IDoc Type )-
In We42, the message type can be assigned to the processing code. But here you will find that along with message type there are two more fields - Message Code & Message Function.
You can use any one these to serve your purpose.
e.g. you can assign
-process code P1 to message type M with Message code 1
-process code P2 to message type M with Message code 2
Further these process types can be configured to call separate FMs.
Now depending on IDOC types your external system should populate the message type as well as Message code so that accordingly process code will be determined at the time of inbound processing.
I hope it's clear & correct
Thanks,
Ram

In which table cound i find the info on EDI standard Message type??

Example
EDI standard Message type Business process
EDIFACT ORDERS Purchase order
INVOIC Invoice
ANSI X12 850 Purchase order
810 Invoice
Like those 850..810..etc info, i dont know from which table could i find the related info?
Thanks.

Hi Hoo,
Electronic Data Interchange (or EDI) refers to the use of computers in formatting and exchanging business information using internationally recognized standards and formats. Standards organizations throughout the world have defined hundreds of document types to create a universal language for companies to conduct business while using dissimilar systems and processes. Common business documents, such as the invoice, purchase order, production planning schedule, ship manifest, and customs declaration, have been standardized and are sent and received electronically over private secure networks (Value-Added Networks - VANs) and the Internet.
So EDI is not an SAP product, It is a method to exchange the data over internet.
You dont get any information in any table in SAP. SAP supports EDI to exchange the data over internet. There are no. of third party EDI tools to connect to SAP.
following is link to know more about EDI message types.
http://www.edifactory.de/messages.php?s=D96A

URGENT! Idoc Message Type FIDCC2 Not Posting CO Documents

Hi Everyone,
Our company is just about to begin using message type FIDCC2 to post entries through FB60/FB65 and FB50. When you manually enter an entry through any of these transactions, an FI, CCA and PCA document are all created simultaneously. However, when posting an identical entry through message type FIDCC2, only an FI document is created. Why are the other documents not being created and is there something that I am missing from configuration or some sort of trigger that is supposed to create the other entries? Please assist as this is extremely urgent.
Thanks to all that can assist,
Pete

Hi Peter,
Is your company uses any of the profitability segment fields as well? If so how are you updating this information on to the FIDCC2 idoc and how are you generating any COPA document simultaneously. I am in the same situation and my FIDCC2 idoc updates the FI, CO, PCA components but not the COPA. I am not sure where to populae the Profitability segments on the FIDCC2 type. Please share if you have same issues in your company.
Regards
Elphick

RFC to RFC - Error in the target RFC - Message type I

Dear all,
I am making a message using from RFC(ECC 6.0) to RFC(ECC 5.0).
It happens an error(System_Failure) because in the target RFC(source code), there is a message type I. I can't take off the message, so how can I create my message without error?
Best Regards,
Fernando

hi,
are you using a BAPI with direct commit fomr RFC adapter?
read info about parameter:
Commit Control for Individual BAPI Calls
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/content.htm
"I" should not affect the commit
if you have the commit inside then don't raise exception
or raise it inside another Function module that will serve as a wrapper
to the one you use)
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Difference in Fault message types & exceptions for Webservice in ABAP

Hello all,
I am relatively new to the web service framework in SAP. My problem scenario is as follows.
I have a WSDL file of a webservice from 3rd party non-SAP s/w and I want to replicate the same webservice into SAP by creating FM in SE37 with same imp/exp parameters and functionality.
So I first created a consumer proxy using the external WSDL file of non-SAP webservice. This generated imp/exp DDIC structures in SAP. Now I created a RFC FM in SE37 with similar Imp/exp parameters and relesed this FM as a webservice. I then created another consumer proxy using WSDL of this newly created webservice in SAP.
In the old consumer proxy I see a structure as SOAPFault as a Fault message type which has 3 fields ERRORCODE, TEXT, DETAILS but in the newly created consumer proxy I don't see Fault message types but i see exceptions which i mentioned in exception tabs while creating the FM. The imp/exp parameters are identical.
So my question is while creating a web service in SAP using a FM in SE37, what needs to be done in order to get the Fault message types getting created automatically when we create a consumer proxy for this webserivice?
Also based on the WSDL of 3rd party system , can i replicate the same web service in SAP ?
Appreciate your expert advice on this.
BR
Nilesh Puranik

Hi Krishna,
I've read the SAP description about Fault Message Types but I'm still struggling on how to use them correctly.
Why do we need them if I can't do nothing with it on the BPM side? After the mapping of the FMT, I'd like to acess it so that I can send a description back to the original system...The thing is, in BPM you can't acess the FMT, you can only create a new BRANCH (on a block step) for it...
I've tried to acess the description text on trace which comes with the message, but it seems that the trace only serves for posting info, and not for getting any...
The Mapping Runtime Constants have some information where you can read some descriptions, but nothing related to the errors....You can read the Receiver service, sender, interface_namespace, but nothing from the ERROR tag...
Is there a way to get the description? Or anything related to the error tag?
Thanks in advance

Guide for Fault Message Type

Hi,
I search a guide for configuration a "Fault Message Type".
I have read, if there is a mapping error, XI will create a error handling in a xml-file.
But I can not find this file.
Can you help me please?
Thanks.
Regards
Stefan

Hi Stefan,
Exception can be declared in BPM steps like Transform,send,Block and handled in Exception Branch.
TO know more about BPM and its exception go throught this link,
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
Cheers,
Rashmi

[HR] About message type HRSM_D

Similar Messages

Maybe you are looking for