IDOC reprocessing with new conversion rules

Hi All,
we've created IDOCs and after the creation the conversion rules are changed. Now we want to reprocess the IDOC's and in the reprocessing we want to use the new conversion rules.
I've tried just reprocessing, I also tried WE19, but with these 2 the conversion rules seem to left untouched.
Has anyone a solution were I can reprocess making use of the new rules?
kind regards,
Pieter

Hi,
I've debugged the reprocessing of the idoc and it seems indeed I had to change the status, however not all statusses result in reprocessing of the rules. Status '29' Error in ALE Service works. So my problem is solved.
Thank you.
kind regards,
Pieter

Similar Messages

Data records in an IDoc getting erased, when conversion rules are defined

Hello ,
We are sending IDocs of message type GLMAST & COELEM from a system(version 4.7) to another system (version 4.6B).
The segment data in the IDocs are changed using the user exit enhancement KKCD0001. The function exits used are EXIT_SAPFKCIM_001 and EXIT_SAPFKCIM_002.
If there is no conversion rule defined in the receiver system, for the segments, the IDocs are posted correctly in the receiving system. But if we define conversion rules , then the data records for all the segments for which conversion rule is defined are getting erased, and an error occurs during processing of IDocs
Please let me know what can be the the reason behind this issue..And how to solve this..
Thanks in advance,
Afsar

Issue solved

IDOC Posting with new fields in VA01

Hi,
Previously i asked for creating New fields in VA01 screen.
i got that now i need to create a sales order based on the Inbound IDOC which i get and i will be getting new fields which are created .
And this Fields data is coming from an Extension to the Standard IDOC. Sales order is getting created but the new fields are not getting populated nor stored in VBAK Table.
pls let me know why is this.And provide me with a soultion.
MG.

Hi,
i had a similar problem in my last assignment .
I think you are using IDOC_INPUT_ORDERS F/M for Posting the IDOC.
Here once you go into the code at line number 116 you can see that they are calling Transaction VA01 for posting the sales order .
If you go into any perform there you would be having the User Exits . Use the exits and you need to process the IDOC in the Foreground so that you can catch the Screen flow and the screen number , as you do in SHDB.
Now you need to make sure that you are getting the new screens there where you have desigined the fields on the screen.
And write the BDC Code with proper OK Codes before the Save ok code SICH is reached .
And make sure that you are writing the code at the header level only as you need to update the VBAK Table.
As this is a single screen you can directly write the BDC code for populating the fields data and at last make sure that the ok-code you are giving is the right one.
Pls let me know if this problem is solved , i need to check the code in which exit i have written . But here it would be the same EXIt i think .
the exit name is EXIT_SAPLVEDA_002 .
Pls check this and let me know.
Regards,
Naidu.

Idoc edited with new values

Hi,
I have an idoc with no 32945925 which is in green with status 70 but this idoc is edited and a new idoc 33010450 has been generated but this idoc is in yellow with status 69.
How far I can assure that idoc 33010450 has been successfully processed and it has been posted Or do i need to do anything manually because it is in yellow status.
Regards,
Karthik.k

Hi,
Normally the idoc will not be processed.It depends on the partner profile configuration.If it is set that it should be processed immediately it will be done automatically.But normally it is set as collect idocs,In that case we have to process them separately.
Regards,
Sasi

Idoc enhancement with new fields and refresh in MII 12.1

Hello all,
I'm using one standard idoc LOIPLO to transfer planned orders from ERP to SAP ME 5.2
I have enhanced this idoc to add some new "custom fields" -> On the ERP side I can see my new fields in the idoc, but when idoc is received in MII, I don't see my new fields (it's still the "old" idoc version). In 5.1, I remember that we had to stop/start the message listener in MII and new fields were available, but in 5.2 it does not work.
-> Message listener is now configured at Netweaver level and we stop/start it, but the new fields are not in.
Any idea how to "refresh" the idoc version in MII ?
Thanks and regards,
Michaël.

Restart the NW server
Restarting the Java process should be enough...
Perhaps also via the "cache refresh" tool normally used for Webdynpro stuffs...

Query about ALE conversion rule

Hi,
   I am trying to copy an ALE conversion rule from one system to another.
   In the rule, for one of the variables, the option 'Set Variable' is selected and a variable '&PRTMVxxxx' (Name changed)
   is set under 'Rule Type'.
   I was not aware of how this variable gets filled or what additional setting is required.
   Could someone help me out with this option under the conversion rules?
Regards,
Sudeep

Hi Gaurav,
I have exactly the same problem that you had back in late 2006, with the Conversion Rules somehow not passing the data to the IDOC segment.
The IDOC segment is cleared of all values with the Conversion Rule active.
I have managed to determine that the exit is working properly, at least to the point where it is finished in EXIT_SAPFKCIM_001, and SENDER_SET_NEW is filled correctly.
Did you manage to figure out what was wrong?
Does anyone else know how to get this working?
Thanks,
Bruno

How to implement a conversion rule in KC7R (External Data transfer-Tool)

Hi,
I am familiar with programming conversion rules in ABAP in the LSMW and IS-U Migration workbench.
Unfortunately we have to work with EDT (transaction KCLJ).
I need to implement a simple conversion rule: migration file has the external BP number BPEXT and I must retrieve the internalone (PARTNER) for the migration program.
So I must implement a short ABAP code (select single * from BUT000 ...).
Now I see that in KC7R you can use constants and conversion rules. There are also "General Ruels" and "conversion routines".
Can someone explain how to implement this simple ABAP conversion rule in KC7R giving a short example?
This would be great.
EDT is the workst of all SAP Standard Migration Tools I have seen.....
Kind regards,
Thomas

Thomas,
Coud you please share your findings as I am now in a similar to your original post.
ie I too would like to know how to code convesions for use within the transfer rules used by KCLJ.
Kind Regards,
Hiten Mistry.

IDOC reprocessing including conversion rules

with BD87 you can reprocess a IDOC, which was not properly processed because of any reasons.
For me it looks like that using BD87 conversion rules maintained for the IDOC message type are not reprocessed again. Is there any way to force the system to include the processing of conversion rules in the reprocess step.
Thanks for any help
Marita

Hi Marita,
Have you tried with the application RBDMANI2
Shylesh

ALE IDoc Conversion Rule or BADI

Hi,
I'm new to ALE IDoc. I have a requirement to hide some sensitive data field for the HR information when outbound the Idoc.
Example, I need to outbound the IT8 Basic Pay with payscale area etc but not with the basic pay amount. I can convert the basic pay amount to zero when the idoc is being created.
I've searched through some information and found out that there are several ways to achieve it. However, I'm not sure which one is a better way.
Is it using the Conversion Rule (BD62) or using Badi or Idoc Reduction method is better?
Kindly give me some hints as I'm very confuse of which one is the better solution.
Many thanks in advance.

No user exit is needed for conversion rule.
However, you should remember that conversion rules are applied segment fields for a particular message type. So wherever the IDoc message type is used the rule will be applied. If you want to associate the rule for any other condition in addition to message type better to go with a BADI
These are steps to create and apply a conversion rule to a message type:
1. Transaction BD62 - Create conversion rule and assign it to a IDoc segment
2. Transaction BD79 - Define the conversion rule by selecting your field and clicking display button. Once inside you can use various options like set constant to map 0 to the basic pay
3. Finally assign the conversion rule to your message type using BD55
As for BADIs, IDOC_DATA_MAPPER is also suited for your requirement, the method PROCESS, allows you to manipulate your IDoc fields whichever way you want. You get the control record, data records, using which you can restrict your manipulation to specific message type or other conditions
To above post, BADI IDOC_CREATION_CHECK should not be used for mappings/conversions as its specific purpose is to stop creation of an IDoc under required conditions

Errors with the global conversion rule for the field 0SOURSYSTEM.

Hello Gurus,
We are implementing CRM Activities. I enhanced the data source and when I add new info objects to 0SAL_DS01 DSO and trying to activate I'm getting there errors. Can some one please help me out in this problem?
Error in global conversion rule for InfoObject 0SOURSYSTEM
Message no. RSAR263
Diagnosis
Errors with the global conversion rule for the field 0SOURSYSTEM.
System Response
The function module delivers the following error message:
Field "" is unknown. It is neither in one of t
Procedure
Check the definition of the global conversion rule for an InfoObject
What does this error mean? We are using BI 7.
Thanks
RKR

I have around 9 source systems, do I have to maintain data for all of them for 0SOURCESYSTEM?
I set data for CRM system and then tried to activate.. but still I'm getting same error.
I;m getting this warning too...
InfoObject 0FISCVARNT needs to be in key for DataStore object C_0SAL_D
Message no. RSDODSO123
Diagnosis
Characteristic 0FISCVARNT is included in the data part of ODS object C_0SAL_D.
System Response
The fiscal year variant cannot be used in the update rules for calculating business hour characteristics.
Does this matter???
Thanks
RKR
Message was edited by:
RKR M

Reduced message type - Idoc without conversion rules

Hi Friends,
Am facing a strange situation while converting the Material Master data from 4.7b to ECC using BD21 transaction with reduced custom message type. I have reduced the standard msg type MATMAS05 using BD53 for the required field mapping both systems and I written the code using the exit EXIT_SAPLMV01_002 based on client req.
The situation is that sometimes IDocs are failing and the error shows that some fields which I have not selected in E1MARAM segment of the reduced msg type are populated with some values(ex: zeroes-0, slash-/,spaces)
Note: Conversion rules are not needed for this scenario.
Please help me out how to get rid of this '/ ' or spaces which appear for unselected fields in outbound Idoc using reduced message type ?
Thanks
Saravanan

Hi,
Please check the documentation in WE60 tcode and see if the fields are required to be passed...
Regards,
Nagaraj

Send custom error message using IDoc conversion rule?

Hello,
I am using an Idoc conversion rule in BD79 to load cost centers. In my conversion rule I use a conversion exit function module to concatenate 2 specific characters and sending cost center value together and then this output value placed in the receiving cost center field. This works fine, but now I want to send a custom error message to the idoc and fail the idoc if the sending cost center value is greater than 8 digits.
Does anyone know how to send an error message or update an idoc with an error message using a conversion rule (bd79)?
Thank you,
Rhonda

Hi Rhonda,
Any luck on the below.. i have a similar issue...
Sorry to hijack your thread...

Idoc conversion rule

Hi,
What is idoc conversion rule? Why we need this?
While upgrading from 4.7 to ECC 6.0 what all precautions need to be taken for the existing standard idocs and custom idocs in the system.
Thanks & Regards,
Soumya.

Hi,
ALE allows the user to perform an SAP transaction in the sending system, after-which the following steps occur:
1 or more communication IDocs (intermediate documents: container for the application data) are created in the sending system database. An ALE distribution model, that needs to have been configured, determines which systems the IDocs are to be sent
These communication IDocs, that contain the relevant application data of the transaction that was performed, are then passed to the ALE communication layer
This layer performs an RFC call, using the port definition and an RFC destination determined through the customer model
The IDocs are then transferred to the respective receiving systems. These could be SAP R/3, R/2 or external systems
If the receiving system is an SAP system then:
In the case of master data distribution the same transaction that was performed on the sending system is again performed on the receiving system with the data contained in the IDoc. This allows the data to go through the SAP checks before posting occurs
In the case of transaction scenarios the relevant data is passed to the respective transactions in order to load the required application document. Eg. A PO is loaded on the sending side, yet a SO is created on the receiving system
Master data has another difference:
It can be set up in such a way that any changes made to specific fields in master data tables can automatically trigger off the ALE distribution process for that particular master data object
If a master data object is created or changed on a sending system and distributed to another system the respective transaction is used to either create or change that respective master data object on the receiving system
In general, if standard SAP can't perform the task required then neither can ALE. It doesn't add functionality, it merely decouples it and allows you to distribute it onto other remote systems.
The Detail as described by SAP
In the output processing one of the function modules of the application creates an IDoc, the so-called master IDoc. This IDoc is sent to the ALE layer where the following processing steps are applied:
Outbound processing
Receiver determination
An IDoc is similar to a normal letter in that it has a sender and a receiver. If the receiver has not been explicitly identified by the application, then the ALE layer uses the customer distribution model to help determine the receivers for the message.
The ALE layer can find out from the model whether any distributed systems should receive the message and, if so, then how many. The result may be that one, several or no receivers at all are found.
For each of the distributed systems that have been ascertained to be receiver systems, the data that is specified by the filter objects in the customer distribution model is selected from the master IDoc. This data is then used to fill an IDoc, and the appropriate system is entered as receiver.
Data selection
Segment filtering
Individual segments can be deleted from the IDoc before dispatch by selecting Functions for the IDoc processing -> Settings for filtering in ALE Customizing. The appropriate setting depends on the sending and receiving logical R/3 System.
Field conversion
Receiver-specific field conversions are defined under Functions for the IDoc processing -> Conversions.
General rules can be specified for field conversions; these are important for converting data fields to exchange information between R/2 and R/3 Systems. For example, the field "plant" can be converted from a 2-character field to a 4-character field.
The conversion is done using general EIS conversion tools (Executive Information System).
Version change
SAP ensures that ALE functions between different R/3 System releases. By changing the IDoc format you can convert message types of different R/3 releases. SAP Development use the following rules when converting existing message types:
Fields may be appended to a segment type;
Segments can be added;
ALE Customizing keeps a record of which version of each message type is in use for each receiver. The correct version of the communication IDoc is created in the ALE output.
The resulting IDocs (it is possible that several IDocs could be created in the receiver determination) are referred to as communication IDocs and are stored in the database. The dispatch control then decides which of these IDocs should be sent immediately. These are passed to the communications layer and are sent either using the transactional Remote Function Call (RFC) or via file interfaces (e.g. for EDI).
If an error occurs in the ALE layer, the IDoc containing the error is stored and a workflow is created. The ALE administrator can use this workflow to process the error.
Inbound processing
After an IDoc has been successfully transmitted to another system, inbound processing is carried out in the receiver system, involving the following steps in the ALE layer:
Segment filtering
Segment filtering functions the same way in inbound processing as in outbound processing.
Field conversion
Specific field conversions are defined in ALE Customizing.
The conversion itself is performed using general conversion tools from the EIS area (Executive Information System).
Generalized rules can be defined. The ALE implementation guide describes how the conversion rules can be specified.
One set of rules is created for each IDoc segment and rules are defined for each segment field.
The rules for converting data fields from an R/2-specific format to an R/3 format can be defined in this way. An example of this R/2 - R/3 conversion is the conversion of the plant field from a 2 character field to a 4 character field.
Data transfer to the application
Input control
When the IDocs have been written to the database, they can be imported by the receiver application.
IDocs can be passed to the application either immediately on arrival or can follow in batch.
You can post an inbound IDoc in three ways:
by calling a function module directly: A function is called that imports the IDoc directly. An error workflow will be started only if an error occurs.
by starting a SAP Business Workflow. A workflow is the sequence of steps to post an IDoc.
by starting a work item A single step performs the IDoc posting.
The standard inbound processing setting is that ALE calls a function module directly. For information about SAP Business Workflow alternatives refer to the online help for ALE programming.

How can you remove old conversations from the iMac. Even when I remove them they return when I start a new conversation with the same person. Only happens on iMac with the Beta iMessage program

How do you remove an old conversation using the Beta iMessage on an iMac. When I open a new conversation with the same person the old conversation comes back

Hi,
Previously iChat had tried a Last Chat/IM option when using Saved Transcripts - which itself was an option.
iChat has also tried "Saving" the Last Chat by leaving a Chat window open and using something similar to the Lion method of showing an app in the state is was closed in.
In Messages the option to Save Transcripts has been removed and Chats or all types are saved as a matter of course.
What this tends to mean for your iChat style Buddy Chats is that it opens all the Transcripts for that buddy as a sort of History you can scroll back through if you want (I have some Buddies with saved chats gong back to 2004)
With the Syncing of iMessages with iPhones and iPads (or Touches) then it seems this works slightly differently.
Although you can delete the chat and the contents of the Chat as separate action it is true that in the Beta as soon as you connect to the same Contact that the contents of the previous chats are shown to you.
I have found that Messages stores a data base of info on iMessages in Your Home Folder/Library/Messages
I have found that deleting this chat-db removes the "History" that keep popping up.
By default the Saved "iChats" are also stored in the Home Folder/Documents/iChats (At least this is the default place iChat used and they go to the same iChats folder where ever you had it)
Some people claim removing iMessages saved here stops the "History" reappearing.
In Lion the only access to the Home Folder/Library is via the Finder's Go Menu and hiding down the ALT key
10:00 PM Sunday; June 10, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.4)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.7.4),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Set JArray values with invalid key value: "LastUpdatedTime" on new alert rule creation

Hey all!
I'm trying to create a new alert rule using version 0.9.11 of the Monitoring Library and am getting this error on alertsClient.rules.CreateOrUpdate:
"Set JArray values with invalid key value: "LastUpdatedTime". Array position index expected."
That's interesting because LastUpdatedTime is a DateTime object, and whether I set it or I don't, if I set a breakpoint, it does set itself correctly, but the API appears to be expecting a JSON hash?
I've tested alertsClient and I'm able to get existing alerts (also metrics with metrics client), so I don't believe it's an access issue.
Any ideas?
The full code I'm using for the test (borrowed virtually verbatim from the Cloud Cover video
here):
Rule newRule = new Rule
Name = "CPU Over 90%",
Id = Guid.NewGuid().ToString(),
Description = "CPU Has been over 90% for 5 minutes",
IsEnabled = true,
LastUpdatedTime = DateTime.Now,
Condition = new ThresholdRuleCondition
Operator = Microsoft.WindowsAzure.Management.Monitoring.Alerts.Models.ConditionOperator.GreaterThan,
Threshold = 90,
WindowSize = TimeSpan.FromMinutes(5),
DataSource = new RuleMetricDataSource
MetricName = "Percentage CPU",
ResourceId = "",
MetricNamespace = ResourceIdBuilder.BuildCloudServiceResourceId(<cloudservicename>, <deploymentname>)
RuleAction action = new RuleEmailAction
SendToServiceOwners = true,
newRule.Actions.Add(action);
OperationResponse alertResponse = alertsClient.Rules.CreateOrUpdate(new
RuleCreateOrUpdateParameters { Rule = newRule });
Console.WriteLine("Create alert rule response: " + alertResponse.StatusCode);

Hi Greg,
Thanks for your post!
Error "JArray" has been fixed in the latest nugget package.
Refer to:
http://www.nuget.org/packages/Microsoft.WindowsAzure.Management.Monitoring/
Hope this helps!
Regards,
Sadiqh

IDOC reprocessing with new conversion rules

Similar Messages

Maybe you are looking for