Failed IDoc posting - MATMAS02 - Message MATMAS

Hello Friends,
I have the case of an IDoc failing to get posted when the GTIN number is included in the field EAN11 of segment E1MARMM. I get the following error message:
Unit of measure for material not maintained
Message no. M3 758
Why this error even when the UOM is already maintained for the material.
When the EAN11 number is removed the IDoc gets posted.
Thanks in anticipation.
Kind Regards,
Harisha

Hi
If you are maintain the EAN number in segment E1MARMM, you need to maintain the same in Segment E1MEANM - Master Material European Article Number (MEAN).
In this segment the system is capturing the data relevant to the EAN number
The UOM field may be missing here & the system is giving the error.
Try mainatining it here & reprocess the failed idoc.
Reward points if useful
Is your issue resolved
Thanks & Regards
Kishore

Similar Messages

Idoc posting error message

Dear all,
When I use the WPUK to generate an idoc for pos testing, the system pop up an error message as follow:
No direct postings possible to G/L account 60000000
Message no. M7059
Diagnosis
No direct postings can be made to the G/L account (because it is a reconciliation account).
System Response
The system cannot post the amount to this account.
Procedure
If the system has determined the G/L account, the system setting is faulty. Contact your systems administrator.
If you have entered the G/L account manually, enter a different account or cancel the account entered, so that the system determines an account automatically.
Do anyone know how to check and tackle this issue?
Thanks
Chris

Hi Chris,
They will be several reasons for Error message M7059. Pls check out following points;
(a) Batch Classification (After the implementation of Note 120905)
(b) Respective GL Code may required modification
(c) Check your OBYC settings
(d) After the implementation of Note 790483
Bye,
Muralidhara

Failing Idoc Based on Posts Goods Issue

Hi experts,
I have a requirement where I need to check whether a STO exists for the idoc PORDCR102. Another requirement is to check Post Goods Issue is present. If STO exists and PGI exists, I need to fail the idoc. How to do this(both failing idoc and checking how PGI exists). I am using the user exit EXIT_SAPL2012_001 for this purpose.
Regards,
Sajith

Below are the inbound function module which in turn are calling the bapis to post the document
IDOC_INPUT_PORDCR1 calls BAPI_PO_CREATE1
IDOC_INPUT_PORDCR calls BAPI_PO_CREATE
Search for a exit in BAPI ...which will serve you requirement ....ie. in turn throw a error message if the bapi throws a message the idoc will fail...!

Payroll to FI posting error message - Document Transfer has Failed

Hello experts,
We recently received the following error message when posting Payroll results to FI. This was not done using any process models.
'Document Transfer has Failed'
Does anyone know why it's coming up and more importantly, how to correct it? I looked and found an SNote: 1240870 but that seems to apply to 3PR issues not FI posting.
Anyone else had this error before? How do I correct this? Please help as this error needs to be corrected as soon as possible since FI will be closing the month of November soon.
Thanks,
Suparna

Hi,
http://help.sap.com/saphelp_dimp50/helpdata/en/81/42b1884a3711d189490000e8323c4f/content.htm
The posting run has the status Document transfer has failed. Posting to Accounting did not take place.
Depending on the error that occurred, it may be a good idea to start posting this posting run once again. If the error still occurs and it is not possible to post the posting run, you must delete the posting run and create a new one.
Thanks
Umakanth

Problem LSMW + IDOC method for message type : MATMAS

hi friends,
I am using LSMW + IDOC method Message : MATMAS , idoc type : MATMAS03 .Setting every thing are fine. Finally Material is not created with error "message have been issued number : <idoc number>".
data : material, industry type, material type, description, Basic unit of mesure.
Please help me.
Balaji.T.

Hi,
I have nothing found regarding your issue. But maybe a look at SAP note 638058 will give you a hint.
Regards,
Klaus

IDoc parallel posting for message type of DESADV

The DESADV (Delivery Advice) logic is complex and it takes long time than expected. We want to improve its performance by posting DESADV IDocs in parallel.
Currently, the "Input type" of DESADV's function module is 1, which means parallel run is not enabled. (In tcode BD51). In addition, DESADV is configed as "Immediately" instead of "collected run". We will trigger DESADV every 30 mins, about 500-1000 IDocs will be created automatically and then be posted.
I want to know:
Is it possible to enable DESADV IDocs posting in parallel, how?
Dialog or background is recommended, especially from workload/performance point of view?
Any other concern? such as will data duplicated posting or data lose?
In BD20 (or program RBDAPP01), I noticed there was "Parallel Proc." option which can be selected. Can I just simply change the message type to "collected run" and schedule another background to post those IDocs in parallel?
Any comments is appreciated.
TIA
James

no answer

What are the ways to handle Idocs which are failed to post to R/3

Hi Experts
What are the ways to handle Idocs which are failed to post to R/3 after sucessfully configuration of the Scenario.
Thanks & Regards
Aravind

Hi
Check the Idoc Status in R/3 with WE05.
Idocs will fail in following conditions
1) Idoc will be in error if all the mandatory field are not mapped.
2) If partner profile is not maintained.
3) Most of the times, idocs will be in error due to functional issues.....check the status and take help from functional guys.
Once the error resolved, reprocess the same idoc using BD87
Regards
Abhijit
Edited by: Abhijit Bolakhe on Mar 18, 2010 3:11 PM

What triggers idoc posting in outbound message from sap ?

Do change or create events can be used to trigger Posting to IDOC? Have any body used idoc for outbound message sending from SAP?

Hi Reddy,
Posting IDoc Packets
Two groups of function modules are used to post IDocs:
· Function modules which process IDocs in mass. These transfer packets of IDocs for which individual IDocs are updated in the same Logical Unit of Work (LUW).
· Function modules which process one IDoc per call.
· INPUTTYP contains the code for posting function modules.
To display the function module's INPUTTYP on the ALE Development screen, choose IDoc ® Inbound Processing ® Function Module® Maintain Attributes (BD51).
INPUTTYP can contain the following values:
· "0", for function modules which process IDocs in packets.
"1" and "2" for function modules which process one IDoc per call:
If you post the IDocs immediately, the SAP sending system determines the packet size. ALE inbound processing can recognize if the posting function module allows packet processing and if so, passes the IDoc packet to it. If not, the IDoc packet is split into individual IDocs.
If IDocs are posted in the background, you can specify the size of the IDocs to be generated in the program RBDAPP01.
If you use function modules that can process IDocs in mass, the database load is reduced.
If you group IDocs into packets, this may also be practical for function modules that post inbound IDocs one at a time, because the ALE layer calls the function module several times in the same dialog process, thereby reducing the administrative load on the SAP system.
If program RBDAPP01 carries out the background processing, as a guide, you should use a packet size of between 20 and 100 IDocs.
Packet processing and parallelism complement one another. Packet processing and parallelism complement each other, although in some situations they may compete with each other. If the size of the packet is too big, this may mean that not all the available dialog processes are being used.
Scheduling IDoc Posting
There are two ways of posting IDocs in ALE inbound processing:
·        Immediate processing:
Upon receipt inbound IDocs are immediately released for posting. ALE inbound processing splits the IDoc packets into individual IDocs.
·        Background processing
Inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand.
The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs can be put into packets and then processed.
Perform the following steps:
1.       Set-up background processing (IDoc/ALE area menu):
IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Profiles (WE20)
Then the required setting is: In the detail screen Inbound Parameters select the option Trigger by background program.
2.       Schedule posting (ALE customizing):
Transaction SALE ® Set-Up System Monitoring ®
         Posting IDocs in Recipient System ®Schedule
You can also process the IDocs manually by passing them to the posting function module. In ALE Administration choose Monitoring ®Status Monitor (BD87), select the IDocs and then select Process.
Regards,
Kumar.

1 request Idocs created for message type MATMAS

Hi Experts
I have done necessary config.
I have attempted BD10 and BD11.
I have got message that "1 request Idocs created for message type MATMAS"
But iam unable to find the material in target system.
Please suggest what need to be done.
regards
ramSiva

Marias,
And in PI, after having changed the password (why not), have you unlock this user account ? in SU01 of PI, you have a lock button.
if you did it, and changed also the password, as explained, you have perhaps another (or several) program like a RFC destination which uses another password, and so after some exchanges... with a bad/old password, you have your message "too many...", and then the user is again locked...
If you change the password in PI, you should change it in all application which uses this user. I hope you have not the same user from ECC to PI, than from a third-party to PI...
that's why: the use of such technical users have to be referenced in a doc. By this way, if password has to modifiy, we know where we have to update it (mainly in different RFC destination).
Mickael
Edited by: Mickael Huchet on Dec 5, 2011 5:33 PM

IDOc posting error

hai friends
iam getting idocs form xi system (matmas)
in this MBEWM segement is repeting meny times
in this segment BWTAR field some times not having any value
at that time
if the that segement is is first segment then it is posting proparly
but if we get that segement at other than first is not posting .
how can i do this .
pls help me.
srikanth vipparla

Hi ,
It is simple .
1. Just retrieve the data from the Idoc
2 . Put in ur Interanl table table .
3.Upadate the Transaction using appropriate method .
    BAPI or BDC.
FUNCTION z7_idoc_input_ordchg.
""Local Interface:
*" IMPORTING
*"     REFERENCE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     REFERENCE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     REFERENCE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     REFERENCE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     REFERENCE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     REFERENCE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*"     REFERENCE(DOCUMENT_NUMBER) LIKE VBAK-VBELN
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*"      EDI_TEXT STRUCTURE EDIORDTXT1 OPTIONAL
*"      EDI_TEXT_LINES STRUCTURE EDIORDTXT2 OPTIONAL
*& Function module   Z7_IDOC_INPUT_ORDCHG                              *
TITLE        : Inbound Function module                               *
AUTHOR       : Sree M             *
CREATED DATE : 20/MAY/2008                                           *
=====================================================================*
Description : Inbound FUnction module for updating the data in the *
               sale order                                            *
=====================================================================*
Loop at IDOC_CONTRL.
    IF idoc_contrl-idoctp NE 'ORDERS05'.
      MESSAGE e899(f4) WITH text-001.
    ENDIF.
****Retrieving the date from IDOC
   LOOP AT idoc_data WHERE docnum EQ idoc_contrl-docnum.
    CASE idoc_data-segnam.
      WHEN 'E1EDK01'.
        MOVE idoc_data-sdata TO is_e1edk01.
      WHEN 'E1EDP01'.
        MOVE idoc_data-sdata TO is_e1edp01.
        MOVE is_e1edp01-posex TO l_posnr.
        MOVE is_e1edp01-abgrt TO wa_vbap-zzcontract_num.
    ENDCASE.
ENDLOOP.
v_vbeln = is_e1edk01-belnr.
L_POSNR = IS_e1edp01-posex.
Select single * from vbap into wa_vbap
                    where vbeln = v_vbeln
                              and
                     posnr = l_posnr.
If sy-subrc = 0.
    Check ( IS_e1edp01-abgrt NE wa_vbap-zzcontract_num ).
        Wa_vbap-zzcontract_num = IS_e1edp01-abgrt.
****Updating the Transaction
***Here using lock Object I updated
                  CALL FUNCTION 'ENQUEUE_EMVBAP'
                             EXPORTING
                               MODE_VBAP            = 'E'
                               MANDT                = SY-MANDT
                               VBELN                = v_VBELN
                               POSNR                = l_posnr
                              X_VBELN              = ' '
                              X_POSNR              = ' '
                              _SCOPE               = '2'
                              _WAIT                = ' '
                              _COLLECT             = ' '
                            EXCEPTIONS
                              FOREIGN_LOCK         = 1
                              SYSTEM_FAILURE       = 2
                              OTHERS               = 3
                            IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
                            ENDIF.
idoc_status-docnum = idoc_contrl-docnum.
Update vbap from wa_vbap.
    IF SY-SUBRC = 0.
       v_flag = 'X'.
    ENDIF.
         CALL FUNCTION 'DEQUEUE_EMVBAP'
            EXPORTING
             MODE_VBAP       = 'E'
             MANDT           = SY-MANDT
             VBELN           = v_VBELN
             POSNR           = l_posnr
           X_VBELN         = ' '
           X_POSNR         = ' '
          _SCOPE          = '3'
          _SYNCHRON       = ' '
          _COLLECT        = ' '
IF V_FLAG = 'X'.
    idoc_status-status = '53'.
    idoc_status-msgty = 'S'.
    idoc_status-msgid = sy-msgid.
    idoc_status-msgno = sy-msgno.
    idoc_status-msgv1 = sy-msgv1.
    idoc_status-msgv2 = sy-msgv2.
    idoc_status-msgv3 = sy-msgv3.
    idoc_status-msgv4 = sy-msgv4.
    APPEND idoc_status.
   ELSE.
    idoc_status-status = '51'.
    idoc_status-msgty = 'E'.
    idoc_status-msgid = sy-msgid.
    idoc_status-msgno = sy-msgno.
    idoc_status-msgv1 = sy-msgv1.
    idoc_status-msgv2 = sy-msgv2.
    idoc_status-msgv3 = sy-msgv3.
    idoc_status-msgv4 = sy-msgv4.
    APPEND idoc_status.
    return_variables-wf_param = eid.
    return_variables-doc_number = idoc_contrl-docnum.
    APPEND return_variables.
    workflow_result = c_wf_result_error.
    ENDIF.
ENDIF.
ENDLOOP.
ENDFUNCTION.
Rgds
Sree M

Failed IDocs in the Production

Hi,
Can anyone let me know, How Failed Idocs would be handled in the Production System?
Thanks,
Sekhar.J

Hi MxG,
Thanks for your Reply. We may get Status message as 51.
That means "IDoc: 0000000001230290 Status: Application document not posted".
The Reason could be as. No jurisdiction code could be determined.
I should send this message back to PI system which triggers IDoc. How can i handle this?
Thanks,
Sekhar.J

ITunes fails to load. Message is Service Apple Mobile Device failed to start. Verify you have sufficient privileges to start system services. Never had this problem before trying to install this upgrade

iTunes fails to load. Message is "Service Apple Mobile Device failed to start. Verify you have sufficient privileges to start system services." Never had this problem before trying to install this upgrade. How do I fix this?

Dave, same problem here. And I did go in as admin to Administrative Tools, Services, Apple Mobile Devices and tried restarting the service. It seems there is a bug with the newest update, period. All of the normal "easy" steps don't work. Before I remove all of Apple's programs, including Bonjour....I'm running a full system scan.
But the answer will be to remove all of the Apple stuff, then reboot, then use whatever utility you have to remove all temp files...then go download and install it again. This has worked for several people (I read the thread before posting). Win 7 64bit. It just seems that Apple did not thoroughly test this new version. Period.
If Apple reads this...I have many computers...and whenever Apple wants to update something...it just about stops everything else that is going on. Total memory hog, even with 16G RAM and dual quad core processors. It has to learn to play nice with others.
After the scan and I'm sure an hour or two of work...I'll re-post.
Of course if you do image back-ups, as I do, you can simply restore your drive to its previous state and run the previous version of iTunes, declining the update, until Apple gets it right. Depending on the size of your drive, this could take hours. It is a matter of choice, of course.

Idoc with error message when coming from middleware but not in we19

Hi Experts
I am facing a very strange issue !
I have a Z - Idoc type and corresponding inbound function module for creating schedule lines i.e. doing something what me38 does.
When my middleware i.e. Mercator Websphere is sending the idocs, they fail with the error message in the status record as
Field EKET-MENGE (19) does not exist in the screen SAPMM06E 1117.
But when I try processing the same idoc using we19, the scheduling lines are created and the schedule agreement is changed.
Is there any difference between we19 and when idocs come from the middleware ?
Points would be rewareded if useful answers received.
Regards
Shubhankar

Well i think that the problem is with your BDC. there is an option to use standard size in BDC. I think your table control falls short of 19 rows in your program. Please see the thread below and incorporate the same changes in your BDC. I think u might need to record the BDC again.
Re: BDC tabel control for QE01
DATA OPT TYPE CTU_PARAMS.
OPT-DEFSIZE = 'X'.
CALL TRANSACTION 'FB01' USING ITAB OPTIONS FROM OPT.

EDI ANSI X12 and relavent IDOC types and messages...

Hi ,
    Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
210 -Motor Carrier Freight Details and Invoice
240 -Motor Carrier Package Status
753 -Request for Routing Instructions
754 -Routing Instructions
816-ORGANIZATIONAL RELATIONSHIPS
828-Debit Authorization
846- Inventory Inquiry/Advice
870-Order Status Report
Could you please help me?
Thanks and regards,
gowri

EDI ANSI X12 and relavent IDOC types and messages...
Posted: May 25, 2006 8:44 PM        Reply      E-mail this post
Hi Ravi,
     Thanks a lot for the reply. I have already checked this. In the ittoolbox.com is having some info about 214 but not about 210 and 240. I have already gone through the sapgenie.com but could able to get the relevant info on below transactions.I am basically looking for relevant idoc types and messages in SAP for the below ansix12 transactions .
Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
210 -Motor Carrier Freight Details and Invoice
240 -Motor Carrier Package Status
753 -Request for Routing Instructions
754 -Routing Instructions
816-ORGANIZATIONAL RELATIONSHIPS
828-Debit Authorization
846- Inventory Inquiry/Advice
870-Order Status Report

Regarding IDOC posting to create sales order

Hi Friends,
when we are trying to post Idoc to create sales order, Idoc status is showing error as "Enter requested delivery date" with status 51. and error message no is V1394. we found that user is trying to post the Idoc with two delivery dates.
Kindly help me to find out the root cause of this issue....why system is throwing error as "Enter requested delivery date"
Thanks in Advance,
Reagards,
Babu

Hi Babu,
Normally customer will forward 2 types of delivery date
1. Requrested Delivery Date (Goods reaching to the customer door step, EDI qualifier '002')
2. Requested shipping Date (Googs leaving from shipping from warehouse, EDI qualifier '10')
In the above case SAP will take only requested Shipping date which can be mapped at E1EDK03 - DATUM with E1EDK03 - IDDAT is equal to '002'.
Let me know whether you are mapping IDOC with EDI message. If so then you need to map with the EDI qualifier '10'
<< Moderator message - Point begging removed >>
With best regards,
M. Rajendan.
Edited by: Rob Burbank on Jan 4, 2012 9:47 AM

Failed IDoc posting - MATMAS02 - Message MATMAS

Similar Messages

Maybe you are looking for