Dynamic Determination of Target Messge Type (IDoc)

Hello,
we have a IDoc - HTTP scenario. A SYSTAT01 IDoc should be sent back to the sender system setting the status depending on the http response.
The basic scenario works fine, however depending on the value of one field there should be either a STATUS or ZSTATUS message type be sent back. Both are based on the SYSTAT01 IDoc structure and there absolutely no difference in the mapping logic. The two differet message types are used to handle inbound processing in SAP differently.
Question now is, whether I can set the output message type dynamically in ONE message mapping. I tried to set the field MESTYP in the control header, but this does not work, as the MESTYP obviously is always set according to the imported type.
Of course it would work using two different mappings, but I would rather handle ii

Hi,
you cannot change message type in the mapping
but you can have two target messages in one mapping and fill only one of them
Regards,
Michal Krawczyk

Similar Messages

Dynamic determination of currency translation type

Dear all,
we have a requirement for some reports in Business Warehouse (NetWeaver 7.3) regarding the currency conversion type. In the Report a rolling forecast (always starting with the actual period) with one key figure (e.g. Price) shall be analyzed. The issue is the following: The actual period should use Translation Type A, the following periods, till end of Fiscal Year, Translation Type B and the rest Translation type C.
Example Structure:
Drilldown to Period
03.2014 (actual Month)
06.2014
12.2014
01.2015
05.2015
Key Figure
Price
Price
Price
Price
Price
Price
Price
Translation Type
TT-A
TT-B
TT-B
TT-C
TT-C
Now, is it possible somehow to determine in one key figure the Translation type dynamicaly using the Option "Ex. rate type from variable" in the rscur Transaction.
Our main issue here would be the connection between the time reference and the Translation type.
Thank you in advance for your help!

Hi,
thank you for your fast answer. We use different Translation types for actual data, forecast and plan data. (MBW, FBW and PBW).
Therefore in our example, MBW will be used for all actual Prices, FBW for all forecast-prices and PBW for all plan-Prices.
Forecast-Prices are valid for the actual Fiscal Year (but future periods), Plan Prices are valid for all future Fiscal Years.
E.g.:
Actual Period is 06.2014: MBW
From Period 07.2014 to 12.2014: FBW
From Period 01.2015: PBW.
Now we need a report with a rolling forecast from actual period to actual period + 17.
The report should look exemplary for this month as following:
Key Figure
Price (06.2014)
Price (07.2014)
Price (12.2014)
Price (01.2015)
Price (02.2015)
Used
translation type
MBW
FBW
FBW
PBW
PBW
Material 1
value
value
value
value
value
value
Material 2
value
value
value
value
value
value
The issue we have would be, that due to the dynamic structure of a rolling forecast, a fixed key figure structure (one Price key figure for each period) with directly assigned translation variables is impossible.
I hope that this example is clearer. If you have of course any additional questions, please dont hesitate to ask.

Dynamic determination of IDOC

Hi,
I have a scenario wherein based on a particular KeyField, I need to dynamically determine the IDOC. I haven't used BPM before and I don't know whether this scenario is feasible using BPM.
My approach is creating a data type for the source which will have common fields of both the IDOCs. This data type will hold the data sent by the sender system. Thereafter, I would create 2 message interfaces for each IDOC. Subsequent Message Mapping and Interface Mapping will also be done. In BPM based on the KeyField, I will determine the Message Interface dynamically and post it to the target system.
Kindly advice whether the above approach is right. Is this scenario possible without using BPM. If so, kindly suggest how to proceed.
Thanks in advance.
Bala

Hi Kumar,
Is there any possibilites of coming both the idoc data ? If so, you can do as following.
As you are going to execute 1:N mapping, it is required to have BPM here. (and one more reason is Idoc adapter is not a part of J2EE engine.)
<i>Is this scenario possible without using BPM</i>
>>>If it is not of above case, then you can make use of conditional Interface determination , you can try without BPM
Hope this helps,
Regards,
Moorthy

How to dynamically determine Receivers within BPM

Im trying to design a way to determine my receivers within my BPM process during runtime.   My Scenario is as follows:
SAP IDOC
    V
XI
             XI uses JAVA Mapping MT1 to determine vendors and if customer receives PIDX
                         JAVA Mapping MT2 to creates the PIDX output file if required
V
SENDs to required Vendor (PIDX if required otherwise email)
My problem is how to dynamically determine the appropriate receiving vendor for my PIDX.
I can not use the condition editor on the standard Receiver Determination because the output message (PIDX) doesn't have specific enough information to determine the vendor.
Other than the customer number there are no other values and we don't want to use customer number because each vendor can have multiple customer numbers (hundreds).
I've tried various attempts but none seem to work. This could also be because I have limited knowledge of BPMs and this is my first complex development. Below are the different attempts I've made at dynamically determining the receiver. Any input would be appreciated.
Receiver Scenario 1
I developed an interface mapping with MT1 as input and the SAP Receiver Determination as output. The problem is for me to use this, the interface mapping had to reference the PIDX output (MT2 instead of MT1) which has no data that I can use to determine the receiver.
Receiver Scenario 2
I added a receiver step right before my send step and used the receiver list. This appears to send the PIDX to everyone in the list and there is no way to evaluate or eliminate a name from the list.
Receiver Scenario 3
I created a context object in the Integration Builder and assigned it to a field in MT1. I then added a switch step with a branch for each vendor. Within each specific branch there is a Send step that has the context object name I created in the "Send Context" field. However, on the configuration side Im unable to access the context object which I created on the design side. Whenever I open the condition editor and select the radiobutton for "Context Object" the list does not include the context object I created in the Integration Builder.

Hi,
Try using the enhaced receiver determination concept.
Maybe based on certain field values you can write a UDF which calculates the receiver.
Try this Blog out
Link : [
http://help.sap.com/saphelp_nw70/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm]
Regards,
Abhishek
Award if helpful.

Error in ALE service 29 Could not determine recipients for message type MAT

Hi Experts,
While transferring the material using ALE am getting error 29 ie 'Error in ALE service' and message is 'Could not determine recipients for message type MATFET'.
Also i ve recieved the materials with the proper status al the end am getting the above error.
Kindly help me out.
Thanks in advance.

Hi ,
Status 29 means " partner profile not found " . Please check if the recieving partner is configured properly in WE20 in sender system.
Also make sure that the Port and RFC definations are also completed. If the IDoc is manually triggered then please make sure that control record parameters of the idoc are properly filled - if we miss the details ( like wrong port given , wrong basic type for message type - or extended message type ) then also the idoc will fail in status 29 even though the partner profile is properly configured .
Since your idoc is getting generated i think no issues with BD64 since already interested recipeints were populated in control record of idoc.
Regards
Vikas Chaudhary

Could not determine recipients for message type HRMD_B

Hi,
I am getting below Error in SRM when transferring Org Structure data from HCM system to SRM system in a Idoc. I am using Message type HRMD_ABA and not HRMD_B. I didn't maintain Distribution model for HRMD_B. But in my IDOC status I am seeing below error message for Message type HRMD_ABA Inbound to SRM.
Only I am seeing HRMD_B message type in transactions WE81 and WE82.
Any idea? I appreciate your help.
Could not determine recipients for message type HRMD_B
Message no. B1003
Diagnosis
An IDoc of message type HRMD_B was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
Thanks,
Shears

Hi Shears
Did you find soulution to your issue ??
thanks
Anup

Message no. B1003""Could not determine recipients for message type ACPJMM""

Hi All,
While posting GR in MIGO, an error is showing. I am attaching the error description.
""Could not determine recipients for message type ACPJMM""
Message no. B1003
Diagnosis
An IDoc of message type ACPJMM was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
Yesterday it was not coming and GR was getting posted.. I was doing configurations for CIN and day before yesterday everything was done,all the registers were getting updated. For that I did many customisation in SPRO. I did settings in tax ion goods monement. and in Material master to assign screen sequence for foreign trade data screen. Is any customozation triggerring IDoc? Earlier also this came, that time we got client copy, but the problem is recurring. Its very urgent as we are going to transport SPRO settings to production.
Solutions will be rewarded.
regards
B Shar
Edited by: Ian Wong on Jul 4, 2008 4:48 PM

Hi
If you are not working with ALE & this message comes, then somone has mistakenly activated ALE linkages for IDoc Output in Accounting.
if you want to keep this active & go forward, you need to complete the Distribution model customizng in BD64.
Thanks & Regards
Kishore

Error In MIGO "Could not determine recipients for message type ACPJMM"

Dear all,
At the time of transaction Goods Receipt(MIGO), I am getting the error message "Could not determine recipients for message type ACPJMM".
System Diagnosis is as below
An IDoc of message type ACPJMM was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type
I have check the ALE Settings in we20 and we21
and have assigned the following message types under Logical syste Partner Type
Outbound
ACPJMM
MATMAS
MBGMCR
RSINFO
RSSEND
WHSORD
Inbound
ACPJMM
DEBMAS
FTDABA
FTDACO
FTDACU
INSPECTIONPLAN_CREATE
MATMAS
MBGMCR
RSRQST
WHSCON
I have also created and Assigned a Logical System to the client and have also created a RFC with the same name
I have checked all settings is SALE and they are Fine.
This is a single system
Please help this is really ugrent
Regards
Suhail John

Hi,
Goto table TRWCA (T Code SE30) and deselect all the checked entries.
This should solve your problem.
Regards,
Priyadarshi

Error - Could not determine recipients for message type ACP JMM

Hi Guru's
I am facing a problem while doing goods receipt(migo), "Could not determine recipients for message type ACPJMM".
Right answer will be rewarded
Regards

hi
If you want to deactivate this goto SM30, enter the table TRWCA, deactivate the component
RWEX - Idoc Output, External Accounting.
this should solve your problem.
refer following links
Message type ACPJMM
Message no. B1003""Could not determine recipients for message type ACPJMM""
MIGO and MIRO Problum
regards
kunal
Edited by: kunal ingale on Sep 2, 2008 11:46 AM

Could not determine recipients for message type ACPJMM

Dear Experts,
while i am trying PGI getting error message " Could not determine recipients for message type ACPJMM'
Kindly let me know wt is the reason and where i should changes for getting clear?
Thanks in advance
ishikesh

Hi Ishikesh,
If you want to deactivate this goto SM30, enter the table TRWCA, deactivate the component
RWEX - Idoc Output, External Accounting.
this should solve your problem.
refer following links
[Message type ACPJMM;
[Message no. B1003""Could not determine recipients for message type ACPJMM"";
[MIGO and MIRO Problum;
Regards,
Karthik

Could not determine recipients for message type ACLPAY

Dear friends,
I am getting error while doing Invoice Verification as "Could not determine recipients for message type ACLPAY"
Please advice how to resolve this issue.
Thanks

Hi
This is IDOC settings for message type ACLPAY there is no receipient please check transaction code WE20 and please get in touch with your technical team
Thanks & Regards
Phaneendra

Could not determine recipients for message type BUPA_INBOUND_MAIN_SAVE_M

We are upgrading CRM from 4.0 to 7.0
While synchronizing a business partner from CRM to ECC, the IDOC control Data section shows no information on the "Receiver Information" Section.It also provides error as "Could not determine recipients for message type BUPA_INBOUND_MAIN_SAVE_M" with error No 29, Outbound Error in ALE.
The Message Type (BUPA_INBOUND_MAIN_SAVE_M) and the Basic Type (BUPA_INBOUND_MAIN_SAVE_M03) was not used in the CRM 4.0 and not sure the reason it apprears now in the IDOC.
The relevant BDOC is not created/shown in transaction SMW01.
We have verified WE20,21, BD64 in ECC
Any advice is greatly appreciated.
Regards
Dhina

Hi,
Please check below note if it helpful to you in resolving the issue.
Note 1447734 - Enhancement of message type BUPA_INBOUND_MAIN_SAVE_M
Thanks,
George

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

Is there a way to dynamically determine the number of out parameters for a server side procedure?

Hi,
Below is a helper method used for calling a server-side function which loops through the inbound bindVars parameter to populate the function's IN parameters. Is there a way to dynamically determine the IN/OUT parameters based on the procedure name in the stmt parameter? No members of the CallableStatement class seemed promising, but the getParameterMetaData() method in the PreparedStatement class seemed like it could be helpful lead. However, I have not found any detailed descriptions (yet) of how to use it.
protected Object callStoredFunction(int sqlReturnType, String stmt,
Object[] bindVars) {
CallableStatement st = null;
try {
// 1. Create a JDBC CallabledStatement
st = getDBTransaction().createCallableStatement(
"begin ? := "+stmt+";end;",0);
// 2. Register the first bind variable for the return value
st.registerOutParameter(1, sqlReturnType);
if (bindVars != null) {
// 3. Loop over values for the bind variables passed in, if any
for (int z = 0; z < bindVars.length; z++) {
// 4. Set the value of user-supplied bind vars in the stmt
st.setObject(z + 2, bindVars[z]);
// 5. Set the value of user-supplied bind vars in the stmt
st.executeUpdate();
// 6. Return the value of the first bind variable
return st.getObject(1);
catch (SQLException e) {
throw new JboException(e);
finally {
if (st != null) {
try {
// 7. Close the statement
st.close();
catch (SQLException e) {}
James

The PreparedStatement.getParameterMetaData() object is exactly what you need for this task.
Once you have the ParameterMetaData you can ask it how many parameters are present and which mode they are. The parameters are numbered from 1 to n and you can use ParameterMetaData.getParameterMode(1); to get the mode of the 1st parameter. The modes are defined as static values in the ParameterMetaData object. Check out the doc at http://docs.oracle.com/javase/7/docs/api/java/sql/ParameterMetaData.html
Timo

Error while updating to target 0PUR_C01 (type INFOCUBE)

Dear Friends
I am facing the problem while loading data through DTP from PSA to cube(Target).Problem occurring is at 0FISCPER.
The error shown is as below:
Data Package 2: Errors During Processing >>> Updating to InfoCube 0PUR_C01 >>
Error while updating to target 0PUR_C01 (type INFOCUBE)
Messages for 101 data records saved; request is red acc. to configuration
Processing Terminated
display for error records: No fiscal year variant specified
DTP request location:
Error Location: Operation Type: VAL_SID_CONVERT
Error Location: Operation Name: 0FISCPER
please give me helpful suggestion. I m w8ing for ur reply. I need ur needful comments.

Yes it is direct mapping with Entry date (SYDAT). But how should i solve this problem.
In PSA, for that Entry date giving the values:
11.02.2009
12.02.2009
13.02.2009
14.02.2009
16.02.2009
17.02.2009
18.02.2009
21.02.2009
23.02.2009
25.02.2009
03.03.2009
05.03.2009

Dynamic Determination of Target Messge Type (IDoc)

Similar Messages

Maybe you are looking for