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

Similar Messages

K9AGM2 Mobo PS2 Mouse POST Error Message

Bios AMI v02.61
Recently the USB mouse connected to the system died and I had to temporarily attach a PS2 mouse to install a replacement and all this works fine. However when I turn on the PC now I get a POST error message "PS2 mouse not found press F1 to continue". How can I I get rid of this tiny annoyance? I have searched the bios options and reset the CMOS to no avail.
TIA,
Colin

Quote from: corkyboy on 26-November-07, 16:31:31
I read the Moan Guide but could not find any references that were helpful. As to the origin of the board, it was purchased from a retailer here in Australia and the manual describes it as a K9AGM2(MS-7327 SERIES) and has the AMD 690G/690V chipset. Have to say in all respects it is a great little mobo.
Colin
"I read the Moan Guide but could not find any references that were helpful."
We need Full details about your system, Moan Guide shows what we need. Example in my signature.
Please provide full details about your system. ID board with Everest:
http://www.lavalys.com:8081/beta/everestultimate_build_1180_y1obfjxk7ls.zip
or look here how to ID board: https://forum-en.msi.com/index.php?topic=107777.msg798546#msg798546

K9AGM3 Mobo PS2 Mouse POST Error Message

I connected a wireless USB combo mouse+keyboard and every time I turn on the PC, I get a POST error message:
"PS2 mouse not found. Press F1 to continue"
I tried to update BIOS using the Live update Series but it informed me that I had the lattest version
Also, there is no halt on errors option in BIOS menu
How can I get rid of this annoyance?

Quote from: dpanteli on 12-January-08, 18:17:06
I connected a wireless USB combo mouse+keyboard and every time I turn on the PC, I get a POST error message:
"PS2 mouse not found. Press F1 to continue"
I tried to update BIOS using the Live update Series but it informed me that I had the lattest version
Also, there is no halt on errors option in BIOS menu
How can I get rid of this annoyance?
I have K9AGM3-FIH board, and it's suposed to be HTPC board, and what I get, I can't normally run my home theater without keyboard and mouse , because of "Press F1 to continue". How can I press F1 with remote ??? Every cheapest MB has halt on error option in bios. C'mon MSI, make a proper bios for this board.

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

Error on outbound processing (- to IDoc), nodetailed error message

Hi guys!
I'm facing a problem with sending IDocs to R/3. My messages have red flag in outbound status, but there is no detailed error message. Everything seems to be ok, but my IDoc doesn't arrive to R/3 and there is that red flag in XI.
What could cause this? It seems like there is some communication problem. Any ideas?
Thank you,
Olian

Hi,
IT will give the status number,what is the status number in IDOC check it and update the thread.
if u find its a data problem u can debugg the FM,go to WE19 and give ur IDOC number and there u will find the option start out bound processing form this opion u can debugg the code and know wat is the error.
Check ur ALE settings.
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Regards,
Phani
Reward points if Helpful

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

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.

IDOC POsting Error: Transition no. OBJ_SYS is blocked by another user

Hi Experts,
I m sending the XML from a third party system into SAP using XI as middleware for IDOC posting (FB01).
I m getting an error <b>Transition no. <xx> is blocked by another user</b> while sending intercompany and cash applications. SAP is unable to process such XML directly.
But if i login to SAP and mannually post the IDOC, it is getting posted successfully.
Any idea what may be the cause?
Useful answers will be rewarded for sure.
Regards
DhanyaR Nair

Hi Dhanya,
        In your inbound idoc processing program, pls do use the lock mechanism for the FI document which you are processing and if it cannot be locked then keep it on wait for sometime and check for the same.
        If its a standard program check whether it can be done in XI.
      When SAP is locking the transaction it will be unlocked after the commit work and hence its happening.
The reason why you may not be getting this in individual processing is that you are doing the same thru a single session. And the lock if am not wrong is happening in table level and not in record level.
Cheers
JK

Posting errors : message 3G 319

Hello,
While posting payroll results to FI(PC00_M99_CIPE), an employee has the following error (message 3G 319) :
"Customizing for wage type 5402 was changed". is it a retro error? or another reason?
Please help to resolve this.
BR,
K.

Dear Karim,
Kindly check the error with output log it will be for some earlier(retro) period(P-previous Period) type.As it is not finding the relevant wagetype for some retro period it is giving error now during posting.
In that case kindly Include the wagetype in table V_T52EZ and check simulation for posting for this employee only.
Thanks,
Salil.

Bios Post error message K9N sli AMD 64x2

I have just built as per my profile below.
After POST, and before entering the Windows load, I get this error message.
"Not enough space in Runtime area!!. SMBIOS data will not be available."
I had great difficulty loading drivers from the CD supplied with the board, as the menu did not display the full list of options. I assume this is because the SMBIOS data did not properly indicate board, procesor and operating system detail?
Any help would be greatly appreciated.

All is fixed..
Thank you all for your kind help and interest in the problems of a complete stranger. It just shows how wonderful these forums are. Thank you.
I flashed the BIOS to rev 1.3. this updated and cleared NVram etc.
Flashing was a nightmare.
I had to create a win 98 boot disk, but It would not recognise NTFS drives. Noting the warning not to flash from floppies, I then burnt a CD with the new BIOS, and addressed the CD from a boot floppy with win98 cd drivers.

Invoic01 idoc posting error Lock error 1 &

All,
Has anyone seen this error before with Idoc processing?   If so what causes it?   The idoc status is 51 and the Status detail is
Code                   SAP
message #           999
message type         E
ID                         ZZ
Any ideas on how I can determine this?   We cannot replicate the issue so can't trace/debug.
Thanks
Sandra

Thank you both - I thought it was due to customization but was hoping the code SAP meant it was due to SAP standard.
Anyway, I did what you both told me to do - got the same results. Unfortunately this ZZ seems to be used as a catch all type error message so there are hundreds of abaps that appear when I click on "where used".   I know most of the customized objects so can search on those individually.
Thanks again,
Sandra

IDVD continues to quit, posts error message

Whenever I try to open iDVD, wether it be in the doc or through finder, it automatically quits and comes up with an error message asking if it should send the report to apple. I have tried relaunching it several times and have restarted my computer as well, but nothing seems to work. I would like to avoid re-installing the disk with iLife on it (that came with my computer) but do I have any other options?

Take a look at my several recommendations in this thread: http://discussions.apple.com/message.jspa?messageID=5929010#5929010

IDOC Posting Errors

Hi All,
I have written an IDOC program with IDOC type BOMORD01 and Message type BOMORD. After running the program i am getting the following statuses.
69 - Custom segments added
69 - Segment cannot be identified
56 - /QSACLNT210/LS//BOMORD////
Can anybody please tell me how to rectify the above errors to post the IDOC successfully.
Thanks and Regards,
Vasu.

Hi Nagesh,
Actually i have not created any custom segment. I am filling the BOMORD01 segments only. I dont know why the Custom segment added error is coming.
Regards,
Vasu.

Idoc posting error 51

Hello,
I am getting an error when Posting
IDOC type /AFS/ORDERS05 , error is Entry 00 in T173 does not exist - check your entry.
I am not sure what this error is , is that some segment not filled correctly from my Z Program.
If yes , then what could be that segment.
Regards
Prashant

check werks/plant -T173 seems to does not exists in the master table T001W.
check this, let me know incase of issues

IDOC posting error with dollar values

Hello,
We have recently started posting general ledger transactions via IDOC. We just noticed that a few of the idocs reflect a status 53 however did not create postings. When drilling into the message, it says that there were not valid line items. (meaning lines with 0 dollar value). However all of the records had valid dollar values. I have found a few notes that adress this as an issue in 46B, however we are on 4.7 and all of the suggested code fixes have been implemented already. Has anyone seen this happen?
-Jeff

1. Please check that the process code in the inbound partner profile is correct.
2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.
BR,
Alok

Idoc posting error message

Similar Messages

Maybe you are looking for