Inbound problem for message type WPUUMS

Dear all,
I want to receive the IDOC data for message type WPUUMS from a java server. Currently i am working on sample values for segments
E1WPU01
E1WPU02
E1WPU03
E1WPU04
E1WPU05
E1WXX01
I am facing problems in passing the correct values .
Its throwing a error message status 51.(Application document not posted) IDoc not fully processed.
can you help me with some dummy data for all the fields in the above segments.
reply ASAP
regards
arun

You have to analyze where exactly the problem is.
There are several reasons why the Idoc did not post:
1) The Data you are sending to post document may be wrong. You may have to validate against valid data in Database.
2) Thre may be some mandatory data which you are not passing through IDoc (Idoc data may be missing).
It is not possible to answer a generic question like this with perfect answer.
Best way is to debug and find out why exactly the problem is, if you know the error message (you may see it in Status record of this IDoc).

Similar Messages

BD87 idoc inbound error for message type HRMD_A

Hello there,
I am getting below error while fetching Inbound idoc in tcode BD87, see log below from ST22
Short text
    An SQL error occurred when executing Native SQL.
What happened?
    The error "-10328" occurred in the current database connection "LCA".
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
How to correct the error
    Database error text........: "Mismatch of number of stream members for
     parameter (3) (application 6, database 9)."
    Database error code........: "-10328"
    Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL""
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
    "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU07"
    "SIMSCTRL_EXEC_COM"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SIMSCTRL_EXEC_COM" "(FORM)", or its possible occurrence must be declared in
the
Do we need SAP_APO in order to install LiveCache?
We have below landsacpe
- SAP ECC 6 EHP4 with SQL server 2005 S BACKEND
-LCAPPS Component release 2005_700 with SP
SAPKIBHD05.
- We dont have SAP_APO component
-SAP LiveCache system have MAXDB 7.7.04.29 as backend.
- Live cache client is installed on same SAP ECC system where we have SAP ECC EHP4 system.
any suggestion how to resolve it?
Mani

>
Mani wrote:
> I installed a standalone server and i need it only for SAP HR (specifically Idoc processing in SAP HR Human capital management module). But i am getting error while running ibound idoc process.
> So Do i still need SAP_APO component?
I never heard of this specific scenario for liveCache usage in the past 7 years working in SAP support on the liveCache component.
Might be useful if you provide some more details (documentation, notes, links) that describe this usage scenario.
In any case you will need to have a liveCache version that is compatible to your application ABAP coding.
The error message you posted indicates that your liveCache version does not fit your application version (or vice versa).
> I installed SAP MAxDB and LiveCache buid using Installation master DVD for SAP ERP. So i think i followed the right method as specified in installation guide.
Be precise, please. Which installation guide? There are hundreds of them - not THE installation guide.
> Secondly can you help me something specific to my problem in coding form?
Already did.
> i tried in LC10, using LCA monitoring i am not able to run SQLDBC trace under
> LCA >> LiveCache Monitoring >> Tools
> but i am not able to execute the same, is it a error or we need to configure something?
Well, the liveCache needs to be integrated into the LC10. You'd do this in transaction SM59 - but as you've followed an installation guide, this would have been covered in it...
> Operational status is active green light, below is file status.
>
>
KNLMSG     KnlMsg     1.098.697     28.01.2011     06:59:55     Database Messages     ASCII
> KNLMSGARC     KnlMsgArchive     8.192     28.01.2011     06:59:50     Database Errors     ASCII
> KNLMSGOLD     KnlMsg.old     342.663     28.01.2011     06:59:50     Database Messages (OLD)     ASCII
> KNLTRC     knltrace     6.209.536     28.01.2011     06:59:56     Database Trace (Raw/Binary)     BINARY
> BACKHIST     dbm.knl     570     10.01.2011     06:18:41     Backup History     ASCII
> DBMPRT     dbm.prt     133.843     29.01.2011     11:41:27     Database Manager Log File     ASCII
> DBMPAHI     L00.pah     214.225     10.01.2011     06:18:16     Database Parameter History     ASCII
> LCINIT     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Initialisation     ASCII
> LCINITCMD     lcinit.bat     3.047     28.10.2008     14:45:51     LiveCache Initialisation Script     ASCII
> LCINITHIS     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Initialisation History     ASCII
> INSTPRT     dbm.ins     863.981     10.01.2011     06:18:47     Installation Log File     ASCII
> DIAGDIR     File     0     10.01.2011     06:18:18     Diagnose History     DIRECTORY
> ANALYZER     analyzer     0     29.01.2011     00:00:36     DB Analyzer File     DIRECTORY
> LCTRC#init.his     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
> LCTRC#init.log     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
> LCTRC#_apo_version.txt     lc_apo_version.txt     164     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
>
> any clue whats wrong?
> Mani
The only thing this tells us is: the liveCache instance itself apparently comes up and writes out the standard log files.
That's it.
As I already tried to explain, the problem seems to be the dependence between your application and the liveCache version.
Usually I'd recommend to open a support message for this, but the colleagues would (hopefully) ask the same questions as I did.
regards,
Lars

Trigger inbound BAPI IDOC for message type ACC_GL_POSTING

I configured our SAP system for inbound GL postings -- message Type ACC_GL_POSTING process code BAPI. I successfully tested all the configuration pieces using WE19.
So how do I trigger the inbound process from my external non-SAP system. I would prefer not create a flat file that is passed by calling EDI_DATA_INCOMING. I also do not want to use BAPI_ACC_GL_POSTING_POST. So what RFC enable FM can I call to pass data and trigger the IDOC generation and processing? Is there anything standard?

I will use the standard RFC enabled function module IDOC_INBOUND_SYNCHRONOUS. No custom abap development will be needed.
Message was edited by:
David F

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 while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

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

Can not generate one xsd file for message type in xi

Dear Experts.
I am not able to generate one XSD file from message type from XI 3.0, When i select message type and go to XSD tab then click on export xsd to file, it is generating two xsd files MainSchema.xsd, Schema1.xsd into one zip file, but i need only one xsd file to import it into MDM.
Could you please help
Thanks and Regards.
Sravya.
The following are the two files. MainSchema.xsd, Schema1.xsd .

Hi Harsha,
Thanks lot for the immediate response. Appreciate it.
Now I am able to generate the one xsd with your inputs , but i am not able to load it into mdm with out any changes in the generated XSD from Message Type. the below is only the original root tag, where modification required.
Original Element : MDM_CUST_MASTER_FILE_REQUEST_MT
==============
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:abc.com:MDM_Customer_Master_ECC" targetNamespace="urn:abc.com:MDM_Customer_Master_ECC">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
etc.
Case :.When i modify the above element as below with out xmlns, targetNamespace
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
I can import xsd into mdm with the above modification.
The generated XML out put File from mdm is having message type tag like below
?xml version="1.0" encoding="UTF-8"?>
<MDM_CUST_MASTER_FILE_REQUEST_MT>
<CUSTOMER> </customer> ...
note: no namespace for message type
Result:
1.When i send this xml file into XI it is failing in message mapping because it doesn't have namespace attached to it and failing in message mapping.
Finally i need your help to generate the xsd or data file like below to avoid mapping problem in xi.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MDM_CUST_MASTER_FILE_REQUEST_MT xmlns:ns0=urn:abc.com:MDM_Customer_Master_ECC>
Appreciate your help.
Thanks and Regards.
Sravya.

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

Archiving of ERS messages: maintain archiving parameters for message type

Dear experts,
I have problems creating archive messages for ERS messages in ECC 6.0. I always get message "Maintain archiving parameter(s) for output type ERS (appl. MR)" even if I have done all steps as described in SAP note 391822:
NACE: application "MR", output type "ERS"
details: storage mode "2 Archive only", document type "ZUNSGUTHCD"
processing routine: medium "1 print", program "RM08NAST", form routine "ENTRY_ERS", form "MR_PRINT".
A condition record for message type ERS is existing with function "VN" and medium "1" and date/time "4".
OAC2: document type "ZUNSGUTHCD", document class "PDF", status "x".
OAC3: object type "BUS2081", Doc.type "ZUNSGUTHCD", L "x", Content rep. ID "K1", link "TOA01", retention period "0".
The archive "K1" is existing and working for other documents, but not for ERS.
Something is missing, but I don't find out what. Any help is greatly appreciated, point are given!
Regards, Karsten

Dear experts,
I have problems creating archive messages for ERS messages in ECC 6.0. I always get message "Maintain archiving parameter(s) for output type ERS (appl. MR)" even if I have done all steps as described in SAP note 391822:
NACE: application "MR", output type "ERS"
details: storage mode "2 Archive only", document type "ZUNSGUTHCD"
processing routine: medium "1 print", program "RM08NAST", form routine "ENTRY_ERS", form "MR_PRINT".
A condition record for message type ERS is existing with function "VN" and medium "1" and date/time "4".
OAC2: document type "ZUNSGUTHCD", document class "PDF", status "x".
OAC3: object type "BUS2081", Doc.type "ZUNSGUTHCD", L "x", Content rep. ID "K1", link "TOA01", retention period "0".
The archive "K1" is existing and working for other documents, but not for ERS.
Something is missing, but I don't find out what. Any help is greatly appreciated, point are given!
Regards, Karsten

Too many recipients found for message type (Distribution model)

Hi,
I wanna send Dilvery note using message type DESADV from a SAP system to another non-SAP System.
I have Created port partner profile and distribution model.
But the Problem is the same message type DESADV is used to send Dilvery from SAP System to another SAP Client.
Idoc getting failed and throwing error stating Too many recipients found for message type DESADV in the ALE model .
I am sure we can create the more than one recipients for same message types. I have done it some time back. Any help highly appreciated.
Regards
Raj

This message pops up when SAP can't identify how to distribute the IDoc based on the settings in BD64. Take a look at the settings there, most likely you'll need to add a filter.
The big ALE/EDI/IDoc book suggests that the same IDoc may be distributed to 2 different systems but specific details are not clear. It seems that one system should be configured first (it does mention a need to use a filter) and then somehow menu Edit -> Model View -> Distribute should be used.
I've never done it myself though and have only run into that error when I missed some filter settings in BD64. Hope this helps.

Too many recipients found for message type in the ALE model

Hello Friends,
Please help me in solving this error. I have a Outbound sales order confirmation ORDRSP .
In the distribution model i have defined the sender receiver and message type clearly...
But in va01 after creating sales order extras ->Output->Hearder --->Edit
Output type-- BA00
medium --ALE
Dispatch time : Send Immediately
I am getting a error -
Too many recipients found for message type ORDRSP in the ALE model
Message no. B1130
Diagnosis
In the ALE distribution customer model several recipient systems for IDOCs with message type ORDRSP and filter object type 'KUNNR' with value '100' have been modeled from this system, but only one recipient system is allowed.
Procedure
Please change the ALE distribution customer model so that it allows only one recipient system for the message from this system.
Please help me in solving this error.
Regards,
jeevan

Hi Jeevan,
In BD64, the said problem occurs, since the message type ORDRSP will be configured to different Logical System.
Since you are creating sales orders & Output type, system doesnt knows, to which Logical system, it has to be sent since the Message type exists more than once.
select Your respective Logical System where the Outbound Sales Order Confirmation ORDRSP has been created.
Under the node ORDRSP, add the filter group for Customer.
Double click the Filter group and add the respective Customer No.s to whom the Order confirmation needs to be sent.
Then create Sales Order Confirmation & Output type. Data will be passed(IDoc) to the respective Customer(where the customer no.) exist in the filter.
Hope it solves your Issues.
Regards,
Anbalagan.

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

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

Mapping problem for IDOC Type DESADV

Dear all
I need to change Segment E1EDP07 in the message type DESADV.
I should concatenate VBELN and VGPOS into BSTNK.
I tried to do this with BD79 (Rules for Data Converting). This seems not to work as I can get only 1 sender Field.
So I tried to use the userexit EXIT_SAPLBD11_001, but it seems that this is not used. I have set a break-point for debugging and treated the IDOC with RSNAT00 without any stop.
Do you have any ideas how I can do this?
Herbert

>
Herbert Schlup wrote:
> I have 2 entries for my DWSADV01
>
> 1 with FM IDOC_INPUT_DESADV and the other with IDOC_INPUT_DESADV1
With the first one, you cannot do much, as there is no user exit in it. But in the second one, there is a user exit when the idoc data is parsed the exit name is EXIT_SAPLV55K_004 and is called in the subroutine DESADV_IDOC_PARSE in the function.
But please note that the function IDOC_INPUT_DESADV1 is used with process code DELS for message type DESADV and Idoc type DELVRY01 and IDOC_INPUT_DESADV is used with process code DESA and message type DESADV with IDoc type DESADV01. So you might be using IDOC_INPUT_DESADV function and unfortunately there are no user exits to handle your requirement.
My advice would be to check with the source system or the middleware to define the mapping of these fields according to your requirement. But if that is not possible, then you need to first check which message type and IDoc type you are receiving and proceed accordingly
KR,
Advait

Inbound problem for message type WPUUMS

Similar Messages

Maybe you are looking for