Changing Status Message in ALE

Whenever we post a order, and if that Order contains some error, it should throw a message to workflow inbox, telling the Order Number and the item Number for Error.
For Eg., Actual error defined in SAP is "Document contains same order item more than once", with 1st Parameter as 0000280145 and 2nd parameter as 00001. But in the workflow, the orginal error shows is just the text message described above i.e., "Document contains same order item more than once". I need to change it as "Document 0000280145 contains same order item 00001 more than once". I think, u mite got my requirement clearly.
Also in certain places, if there are more than two errors, it is getting stored in Application Log.
For Eg., Actual Error defined in SAP is "Messages from IDoc processing can be found in application log". When i click the application log, it tells two error messages...
1. Vendor material 97082D is unknown
2. Item 99999 of purchasing document 0001266463 does not exist
It is getting stored in some table (thro EDIDS-APPL_LOG). Even i need to pass this two errors in the workflow, instead of just "Messages from IDoc processing can be found in application log".
Also is there any function module exists or from which table i have to pass this APPL_LOG number, to get the necessary Text.
Is there any way to solve this?
Thanks and Regards,
Vijay G

Requirement looks bit strange to me, if at all the IDoc is not needed to be sent for error message then why to Generate them, just filter out creation of IDocs by setting the Filters in Distribution model.
For your requirements you may want to take a look at Badi HRALE00OUTBOUND_IDOC.
Regards
Shital

Similar Messages

FM for the engineering change number to change status message to release

Hi,
I have a requirement to change the status message of engineering change number(transaction CC31 or CC32 ) automatically through a program. I have a thought of doing BDC but still i want to know any standard FM or class is available. Please help me if you have any suggestions.
Thanks in advance for your help.
Regards
Syed Samdani

Siva,
Did you check in Tcode OMSR.
Assign Fields to Field Selection Group - (OMSR)
Here you can define whether a field is hidden or displayed, or whether an entry is mandatory or optional in material master maintenance by assigning the field to a field selection group in OMSR.
Hope this Helps.
Vinodh Balakrishnan

Change Status/Message from BE to SRM

Hello,
I have the following situation: A SC is transfered to the BE. For some special products an additional item (limit item) is added in the BE to the PO. This results in the following situation:
SRM        BE
1SC         1PO
- P1          - P1
                - P2 (limit item, cat=B)
Currently the status 'Fehler im Ablauf' is set obviously of this additional line item in BE.
My question: Is it possible to change the messages/status (CLEAN_REQREQ_UP, BBP_GET_STATUS_2) which is set while a SC is transfered from SRM to BE in this special situation? Is there a BADI in place which can be used?
Kind regards,
Thomas

Hello,
in SRM7.0 this seems to be a standard behaviour although you can add items to the follow-on document via BADI.
The relevant coding can be found here:
Class: CL_BBP_BS_SPOOL_SC_CRT_CLASSIC
Method: UPDATE_BE_FIELDS
IF lv_srm_items NE lv_be_items. " The backend document exists but does not match SC! Should never happen!
    IF 1 = 0. MESSAGE e178(bbp_pu). ENDIF. " error in backend system, inform sysadmin
    ls_message-msgty = 'E'.
    ls_message-msgid = 'BBP_PU'.
    ls_message-msgno = '178'.
    MESSAGE ID ls_message-msgid TYPE ls_message-msgty NUMBER ls_message-msgno INTO ls_message-message.
    APPEND ls_message TO lt_messages.
    CREATE OBJECT lx_sc_transfer.
    lx_sc_transfer->put_bbp_messages( EXPORTING it_message = lt_messages ).
    RAISE EXCEPTION lx_sc_transfer.
ENDIF.
Kind regards,
Thomas

Custom status message in ALE HRMD_A IDOC

Hi,
We are using HRMD_A idoc for integrating two SAP systems. We want a custom check to be included in the ALE outbound processing, where for example if a field of an infotype is some value then we want to stop the IDOC from being transferred to the target SAP system. IDOC should stop with a custom error message in the status record. Is this possible using any of the user exits?
Thanks in advance,
Shravan

Requirement looks bit strange to me, if at all the IDoc is not needed to be sent for error message then why to Generate them, just filter out creation of IDocs by setting the Filters in Distribution model.
For your requirements you may want to take a look at Badi HRALE00OUTBOUND_IDOC.
Regards
Shital

Status Message in ALE

Whenever we post a order, and if that Order contains some error, it should throw a message to workflow inbox, telling the Order Number and the item Number for Error.
For Eg., Actual error defined in SAP is "Document contains same order item more than once", with 1st Parameter as 0000280145 and 2nd parameter as 00001. But in the workflow, the orginal error shows is just the text message described above i.e., "Document contains same order item more than once". I need to change it as "Document 0000280145 contains same order item 00001 more than once". I think, u mite got my requirement clearly.
Also in certain places, if there are more than two errors, it is getting stored in Application Log.
For Eg., Actual Error defined in SAP is "Messages from IDoc processing can be found in application log". When i click the application log, it tells two error messages...
1. Vendor material 97082D is unknown
2. Item 99999 of purchasing document 0001266463 does not exist
It is getting stored in some table (thro EDIDS-APPL_LOG). Even i need to pass this two errors in the workflow, instead of just "Messages from IDoc processing can be found in application log".
Also is there any function module exists or from which table i have to pass this APPL_LOG number, to get the necessary Text.
Is there any way to solve this?
Thanks and Regards,
Vijay G

Requirement looks bit strange to me, if at all the IDoc is not needed to be sent for error message then why to Generate them, just filter out creation of IDocs by setting the Filters in Distribution model.
For your requirements you may want to take a look at Badi HRALE00OUTBOUND_IDOC.
Regards
Shital

Service desk settings, automatic email status message change

Hi,
I'm working at Solution Manager 7.0 SP16. I've configured and working Service Desk scenario and it works. Now I'm trying configure automatic email at status change of messages, but It doesn't work
I'm following spro transaction, and SAP Note 691393. I am configuring Service Desk Specific Scenario Settings -> Automatic Email at status change.
I've checked:
- SCOT is correctly configured and working OK.
- Business partners emails are mantained.
I made the configuration suggested as described SAP Note 691303 SAP Tutor. Following SAP Tutor I go to transaction sppfcadm->select crm_order->botton "define action profile and actions"->Action Profile(left view) and SLFN0001_ADVANCED(right view)->mode change->new entry...   I follow the next slides at SAP Tutor.
At the end, when I check results, I go to the support message (transaction crm_dno_monitor) to edit-> Fast Entry->service process->status->In process and I press button save. So I go to Transaction data->Actions but any about the send mail action
Please could you help me??
Thanks and Regards
Raul Aguilar

Hi Mahantesh,
The settings that I've defined at the start condition are:
Transaction sppfcadm->select CRM_ORDER->button "Condition Configuration"->button technical names on->select action AI_SDK_STANDARD(double click)->change edit mode->right frame button create and select the new condition "Send an email to the author when status of message changes"->start condition tab->button edit condition->Name: Zsend_email->Condition definition:User status->Operators "="->constant "status profile"->SLFN0001 "Service Desk Status header"->Status E0002 "In process"->boton transfer condition->save button. At the end I have:
&CRM Service Process.User    =
Status&                                  E0002SLFN0001
I create a new support message (help->create support message) -> transaction crm_dno_monitor->open the support message just created->button change->fast entry->service process-> status->In process->button save
In order to test I go to Transaction data->Actions:
I've a line: wth a red circle, Action="send an email to author when status of message has changed" and start condition:
&CRM Service Process.User      =
Status&                                    E0002SLFC0001
Please could you help me?
Thanks and regards
Raul

Change the Status Message description of IDOC

Hi All,
As per the requirement, we need to change the Description of the standard IDOC status messages.
Example:
STANDARD : Status 51 - Application Document not posted
DESIRED : Status 51 - Application Document not posted, can be reprocessed
We have found the maintenance view to change the same : VEDI_STATS.
Is it advisable to do so?
if Yes Why? and if No then Why?
Note: I'll be changing ONLY description and nothing else.

Hi,
I would suggest not to change the status using VEDI_STATS.
.. if you want to change do it at function module level for each message type. where you can change the idoc status to which ever message you want to.
Regards,
Nagaraj

What is the use of change pointer concept in ale?

what is the use of change pointer concept in ale?
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Creation of IDoc:
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

Application failed to return status record to ALE layer after Idoc procesed

Hi,
I am loading a full load to Product category (hierarchies) through process chain.
One of the load failed with the following error. The Idoc has status 51 in BW.
Can some suggest me the process for correcting this.
Thanks
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.

Hi
If this is standard code then you will have to write code to populate the status message in exit. But in case of custom code, the above mentioned solution is best (if coding logic is correct). I have given this solution to many queries and all worked.
Thanks
Anuraag

Reporting Services Point status message errors.

My Reporting Services Point seems to work OK -all reports are available and run correctly both through the console and via the website. However, I am seeing the following warning in the SMS_SRS_REPORTING_POINT status messages every hour:
"The SQL Reporting Services datasource on Reporting point server "Databaseserver.contoso.com" is missing or has been changed outside of Configuration Manager. It will be rebuilt based on the RSP configuration."
Here's what I think is causing the issue, but I don't know how to solve it.
The reports database is on the same remote SQL server as my site database. Because these site systems were installed automatically through the SCCM installation process, they show up in the Servers and Site Systems Role without an intranet FQDN. However,
when I add the RSP to the database server, it creates a new entry because when manually adding site systems SCCM insists on automatically adding the intranet FQDN. So I now have two separate entries for the same server:
\\DBServer01 - component server, site database server, site system
\\DBServer01.contoso.com - component server, reporting services point, site system
Any thoughts on how to stop these errors?

Yes, I know this is an old post, but I’m trying to clean them up.
In the past when I have seen this, they will automatically clean themselves up after a few days. (aka up to a week later). Have it clean itself up yet?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

Change status(Active/Inactive) of file adapter by the external command

Hi, all.
Is it possible to change status(Active/Inactive) of file adapter by the external command?
Let's say, like
"$ switch_file_adapter_status.sh <File Adapter name> <active|inactive>"
or something like that.
Actually, we have the following requirement for the file adapter.
For example, we have many "file adapter to R/3" scenarios and we only want to allow data transfer between 9:00 a.m. to 9:00 p.m.(R/3 service time).
In order to achieve this requirement, one option would be to switch file adapter status between active and inactive by external command line.
And this command will be controlled by the job scheduler(like Tivoli).
Does XI(3.0 or above) have this kind of feature?
Best Regards.

Hi,
I don't think that this is possible.
But one Solution for your problem could be a job on xi who execute the Queue.
So that Adapter work the hole time and send the Message to XI Queue which process them not automatically.
And the XI Queue you can trigger with a Job like normal R/3 Jobs.
Hope that helps,
Regards,
Robin

IChat will not display status messages.

I'm having a problem - iChat will not display any "available" status messages. All away messages display properly, but any unique status messages will not display, nor does the word "available". I have restarted both iChat and my MacBook several times, deleted the com.ichat.AIM preferences file, but it seems nothing I do will make my buddy's unique status messages display.
I did not previously use Chax but downloaded it to see if it would help; it didn't. I'm willing to delete it if it will solve my problem.
Any help?
Thanks!
Message was edited by: Paperclippe

Ok,
As you either suspected or found out the Saved Status Messages are in com.apple.ihat.plist
The fact they didn't display would suggest that they may have become corrupted and the deletion of the .plist would have helped.
BUT you went on to mention that the Available Choice also does not display.
This would suggest one of two things.
1) Either you are not fully Logged in to the AIM servers properly
Do your Buddies see you are On-line and Available ?
Do they perceive your Status change ?
Can you Text chat to people ?
Can you send files or Pic in Text chats ?
Try Deleting com.apple.ichat.AIM.plist and restarting iChat to see if that helps
2) Something about iChat or it's support folders (the bits that make the Available show up), that are at fault.
In this case try deleting com.apple.ichatAgent.plist
This controls which accounts login and help the app to run some of the features such as the Video/Audio part and Text Messaging.
I would do these one at a time just so you know which it was that fixed it.
8:27 PM Friday; June 20, 2008

Inbound IDOC Mass processing - No status message

Hi Friends,
I am updating a database table using inbound IDOC. But in batch job when XI passes multiple IDOCS,
for some IDOCs there is no status message even though i coded for status message.
If i rerun IDOC in BD87 then it work fine.
please help.
regards,
madan

Hi Madan,
Since you are loading multiple idoc to the system due to high load in the production system data is not commiting properly. So use external commit work statement in you code. this will reduce the performance but logic will work.
COMMIT WORK [AND WAIT].
Effect
The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the current SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
It executes all subroutines registered using PERFORM ON COMMIT.
The sequence is based on the order of registration or according to the priority specified using the LEVEL addition. Execution of the following statements is not permitted in a subroutine of this type:
PERFORM ... ON COMMIT|ROLLBACK
COMMIT WORK
ROLLBACK WORK
The statement CALL FUNCTION ... IN UPDATE TASK can be executed.
Triggering an internal event for the Persistence Service of the Object Services.
If event handlers are registered by the Persistence Service, these collect the changes to the objects managed by the Persistence Service and transfer them via CALL FUNCTION ... IN UPDATE TASK to a specific update function module that is registered as the last update module.
This executes all high-priority (VB1) update function modules in the order of their registration and in a common database LUW. If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating), but instead is resumed immediately after COMMIT WORK. However, if the addition AND WAIT is specified, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
When all high-priority update function modules are completed successfully, the statement executes the low-priority (VB2) update function modules in the order of registration together in a common database LUW.
After the execution of high-priority update function modules, the individual function modules registered using CALL FUNCTION ...IN BACKGROUND TASK|UNIT are executed in a separate database LUW for each destination.
Within an update function module started using COMMIT WORK, the execution of statements that lead to a database commit is not permitted. In particular, the following are forbidden:
Thanks,
Raghav

Inbound Processing of iDoc Status Message

Silly me - I thought this would be simple ...
I am currently changing our bank interface from a customized ABAP solution to use more standard SAP utilities (particularly iDocs). I have the configuration set up to use the PAYEXT message type sending PEXR2002 iDocs to a file port. Our bank is receiving these documents and is returning an iDoc status message containing the status of each payment iDoc that they received from us.
My problem is that I can't figure out how to get these status iDocs to update the status of the corresponding PEXR2002 iDoc.
I am trying to execute an RFC interface to apply these status messages to my system using the following OS command:
D:\usr\sap\VPR\SYS\exe\uc\NTAMD64\startrfc.exe -3 -d RT2 -u xxxxxx -p xxxxxx -c 220 -h SPR32K36 -s 00 -F EDI_STATUS_INCOMING -E PORT=ZFI_INT003
The error message that I receive when this is run is:
RFC Call/Exception: SYSTEM_FAILURE
Group             Error Group 104
Key                RFC_ERROR_SYSTEM_FAILURE
Message        Status record 1 is invalid (TABNAM: 'EDI_DC40')
The port (ZFI_INT003) is the file port that is configured for the outbound file. in WE20, this port has the "Status File" tab set to use the logical file name where the status file is being stored on the server. the startrfc command is connecting to the SAP system and opening the status file. I'm not sure where I'm going wrong here.
Can someone please help get me pointed in the right direction? I've obviously missed something here.
Thanks,
Glen

Hi,
call function modules:
EDI_DOCUMENT_OPEN_FOR_PROCESS
   EDI_DOCUMENT_STATUS_SET
   EDI_DOCUMENT_CLOSE_PROCESS
kind regards,
HP

Changing Status Message in ALE

Similar Messages

Maybe you are looking for