Error in PRRW because posting to CO-PA is required

Hi,
I am working with Travel management and we are getting problems in transaction PRRW because the account used in a trip requires posting to CO-PA. I heard that BADI TRIP_POST_FI (method FILL_EXT_RAWDATA) could be implemented to derive and pass the information, working it together with the FI SMOD enhancement ACBAPI01. But I really do not understant how to implement those to make it work. Could anyone give me more information?
Thanks,
Nisha

HI
Is it coming on particular expense types ? or all ?
Also please check HRP and HRT .
Regards,
Muhammad Umer

Similar Messages

I am getting some errors while distilling the post script file.

I am getting some errors while distilling the post script file. please check and suggest me, how to control this?
<PDFX ISO="15930-1:2001" COMPLIANT="true">
PDF/X Compliance Report
1. Summary
   Warnings: The total found in this document was 0.
   Violations: The total found in this document was 0.
   No problems were found in the document.
   This document passes PDF/X-1a:2001 compliance checks.
</PDFX>
Regards,
Jack

@Jack – you were using a joboptions file by Distiller to convert a PostScript file to a PDF/X-1a.
What you get is no error message, just a report, that everything went ok. And in this case I cannot see any advantage using PDF Export for printing to PostScript/distilling to PDF. Ok, maybe one, CS5 and above would export in a background process.
To prevent InDesign flattening transparency, you could use PDF/X-4 as your export setting. You cannot use writing to PostScript for that task.
Check including tags for tagged export to prevent misalignment of text because of a strange bug with PDF Export when you are using 9pt text on 12pt leading or text with a ratio of 9/12 for point size and leading in multicolumn text frames.
Uwe

PS CS4...an unexpected and recoverable error has occurred because you do not have the necessary privileges...then PS Exits.

Hello,
Upon opening CS4 on my iMac I get the message an unexpected and recoverable error has occurred because you do not have the necessary privileges...then PS Exits. I am running OS Mavericks. If I switch to another Admin user account, the problem does not persist and I can run CS 4 with no issue.
I am pasting the text below from the error report. Any help determining the issue would be great. I read a ton of threads about this, but it seems each person has had a different fix result. I have not gone the route of reinstalling OS, but will if needed.

We just tried reinstalling Mavericks and it did not fix the problem. Tried uninstalling all Adobe CS4 and reinstalling again. There is an error report, but this thread will not let me post it without it saying it is SPAM

Error during creation of posting runnumber

Hello there,
I am trying to post a trip using transaction PRFI after the trip has been approved and settled and experiencing the error bellow. Two days ago, I was able to perform this transation PRFI and PRRW succesfully. Please advise.
Leon
*Error during creation of posting run number (->PR1*
*Message no. 56840*

Hi Saathi,
If you need to post the document to AP, all the employees have to be converted as Vendors using T code PRAA. But this wont be required when you run through payroll. I hope the error occured due to not converting the employee as vendor. Pl check & revert.
Thanks,
Nandagopal C

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.

Travel Expense - Posting run error - Error during creation of posting run

Hi Guru's,
Look forward for your insights. Here you go with my question.
We are implementing Expense Mgt with Portal with out scope for payroll in SAP. I have set up Expense type, WT, Symbolic A/c to G/L Accounts. Im performing Unit testing currently.
Created Expense trip in ESS, from R/3 tcode PRAP, have approved trip, and settled through Tcode - PREC.
When I try to create posting run under transfer to accounting, I get following error
Error during creation of posting run number (->PR1
Message no. 56840
I'm not sure why this error was popping up. Appreciate your suggestion.
Regards
Praveen.N

Hi,
Since you are trying to make payment through FI, you need to maintain ur employee as Vendor. You can do it through PRAA.
So while creating posting run for this trip, it checks if the respective Vendor for this employee is maintained or not.
Pls maintain it as vendor and see if the errors are still coming.
Rakesh

Initialization Error: Failed to read POST response

Guys,
I need help, I am cloning ,y PROD DB to a test environment, I did first using my test database and it worked, but running with my PROD failed.
I am using OEMGrid Control, Wind2003, DBOracle9i, I am trying to connect using OEMGC and when start trasnfering "One datafile" via HTTP (I guess is the temp file) fialed with the error: Initialization Error: Failed to read POST response.
Please does anybody have a little idea what could happen?...please I need some guide...I will appreciate so much....Thanks
I tried looking for the error I the only I got was the follwoing:...It looks like a patch
Subject: Oracle Enterprise Manager Management Agent Patch Set Notes for Windows 10g Release 2 (10.2.0.2)
Doc ID: Note:375161.1 Type: README
Last Revision Date: 01-AUG-2006 Status: ARCHIVED
Skip Headers
Oracle® Enterprise Manager Management Agent Patch Set Notes for Windows
10g Release 2 (10.2.0.2)
B31109-01

What is the size of the data file which fails during transfer? I could find one reference on Metalink where the large file size (6GB) resulted in this error but that is in Oracle 10g.

ECC 5.0 database instance install error in database load (post processing)

HI all!
The installation of the environment :
VM SERVER v1.03
ECC 5.0 /WINDOWS SERVER 2003
SQL SERVER 2000 SP3
DB INSTANCE install occur error in database load (post processing) step:
sapinst.log:
INFO 2008-10-16 14:20:54
Creating file C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB\keydb.5.xml.
ERROR 2008-10-16 14:22:29
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPSSEXC.log
ERROR 2008-10-16 14:24:59
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPAPPL2.log
ERROR 2008-10-16 14:24:59
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPSDIC.log
ERROR 2008-10-16 14:26:30
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPPOOL.log
SAPSSEXC.log:
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: START OF LOG: 20081016142100
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Aug 18 2008 23:28:15
D:\usr\sap\IDS\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPSSEXC.cmd -l C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPSSEXC.log -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: D010INC deleted/truncated
Interface access functions from dynamic library dbmssslib.dll loaded.
(IMP) INFO: EndFastLoad failed with <2: Bulk-copy commit unsuccessful:3624 Location: rowset.cpp:5001
Expression: pBind->FCheckForNull ()
SPID: 54
Process ID: 1120
3624 >
(IMP) ERROR: EndFastload: rc = 2
(DB) INFO: D010TAB deleted/truncated
SAPAPPL2.log
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: START OF LOG: 20081016142130
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Aug 18 2008 23:28:15
D:\usr\sap\IDS\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPAPPL2.cmd -l C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPAPPL2.log -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: AGR_1250 deleted/truncated
Interface access functions from dynamic library dbmssslib.dll loaded.
(IMP) INFO: import of AGR_1250 completed (139232 rows) #20081016142200
(DB) INFO: AGR_1251 deleted/truncated
(IMP) INFO: EndFastLoad failed with <2: Bulk-copy commit unsuccessful:2627 Violation of PRIMARY KEY constraint 'AGR_1251~0'. Cannot insert duplicate key in object 'AGR_1251'.
3621 The statement has been terminated.>
(IMP) ERROR: EndFastload: rc = 2
(DB) INFO: AQLTS deleted/truncated
(IMP) INFO: import of AQLTS completed (17526 rows) #20081016142456
(DB) INFO: disconnected from DB
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: END OF LOG: 20081016142456
SAPSDIC.log:
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: START OF LOG: 20081016142230
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Aug 18 2008 23:28:15
D:\usr\sap\IDS\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPSDIC.cmd -l C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPSDIC.log -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DD08L deleted/truncated
Interface access functions from dynamic library dbmssslib.dll loaded.
(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed:3624 Location: p:\sql\ntdbms\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 54
Process ID: 1120
3624 >
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: disconnected from DB
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: END OF LOG: 20081016142437
SAPPOOL.log:
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: START OF LOG: 20081016142530
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Aug 18 2008 23:28:15
D:\usr\sap\IDS\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPPOOL.cmd -l C:\Program Files\sapinst_instdir\ECC_50_ABAP_NUC\DB/SAPPOOL.log -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: ATAB deleted/truncated
Interface access functions from dynamic library dbmssslib.dll loaded.
(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed:3624 Location: p:\sql\ntdbms\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 54
Process ID: 1120
3624 >
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: disconnected from DB
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\IDS\SYS\exe\run/R3load.exe: END OF LOG: 20081016142621
please help! thanks!

VM SERVER v1.03
can you please tell me what you mean with that? VMWare? Is that ESX-Server?
(DB) INFO: connected to DB
(DB) INFO: ATAB deleted/truncated
Interface access functions from dynamic library dbmssslib.dll loaded.
(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed:3624 Location: p:sql
tdbmsstorengdrsinclude
ecord.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 54
Process ID: 1120
3624 >
(IMP) ERROR: ExeFastload: rc = 2
I´ve seen those load problems under VMWare and on boxes hosted as Xen VMs.
Markus

[SOLVED] Alpine - Error sending: No default posting command

Hi, I have installed the Alpine mail client yesterday, and it all works nicely, except I can't send mail. Everytime I try I get this message:
Error sending: No default posting command
I have tried googling around, and from what I understand Alpine uses sendmail by default, but I haven't got it installed, nor I can find it in the repos. Is there any way I can change this? And what can I use to send mail?
Thanks.
Last edited by finferflu (2007-12-26 16:02:13)

I haven't dug it enough yet, and I'm not sure that this is possible, even though Alpine is very customisable as far as I can see.
I'll let you know if I find anything

Error: Application document not posted

hi,
while posting IDOC into R3, I got below error in WE05.
under status records
51 Error: Application document not posted
Account group is not defined in table T077K
reward points always helpful for helpers.
Regards,
Nageswari

HI,
Check the posting program use call transaction, if no analyze the error message and fix the problem. If yes then debug your program step by step until you hit the error screen.
If error in IDoc data , then Exit the IDoc restart from BD87, else problem with application configuration, restart from beginning.
--related Data error contact your Functional team
Also see the below links
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards
Chilla

LSMW IDoc error : APPLICATION DOCUMENT NOT POSTED with error 51

During LSMW matmas04 uploading i m getting error :APPLICATION DOCUMENT NOT POSTED with error 51
Can some one tell why ots coming so.

to check errors check We05 or we02 they are same
in general i think that most of problem is relate to Dates if that your case check that you converted dates to internal format using conversion step i advice use like this function
CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
EXPORTING
DATE_EXTERNAL = ZHEADER-BEDAT
IMPORTING
DATE_INTERNAL = MBEPOH-BEDAT.
<Removed by Moderator>
Message was edited by: Marcelo Ramos

Idoc number have status is 51 Error: Application document not posted

hi friend
i have error in idoc number status 51 Error: Application document not posted. basic type is ORDERS05 Purchasing/Sales
what i do for solve this issue
with regards
dinesh
Edited by: code acess on Feb 9, 2011 4:35 AM

Hi,
{1.how i check in the delivery documents have idoc number ? }
Go into the delivery, output. Check if any output has been triggered for EDI. If yes, then select the output and click on 'Process details' (it is the button just after communication where you give the print name). It will display the Idoc number.
{ what are the required for cofiguration of EDI. Pls Send me the configuration setting . i didnt have help here ..iam expecting configuration setting }
Though it is difficult to share all the config settings in this thread, what I will do is to put in a few steps which are general settings. Only a few things vary.
For EDI / ALE - Idoc the common settings are
a. The port should be enabled for sending and receiving the data thru Idocs. Usually basis does this.
b. Partner profile should be configured in WE20. Example if you are sending a sales order confirmation to ship to party then, You should set up a partner profile in WE20 for partner number in KU (Customer) folder. You can copy any of the existing customer. What you have to make sure is you have added the message type and the Basic Type in the outbound parameters of the partner in WE20. Also, you have to make sure that you are giving the output type and the process type as well.
This is same even when you are receiving the Idocs from customer. Say for example customer PO. However, instead of outbound, you will add all these details in inbound.
Similarly, if you are sending PO to your vendos, then, you have to make changes in folder for partner LS. There are so many other folders as well.
Check WE60/61 for the documentation for what is Basic types, Message types and segments. It is very important for you to know about these when you are dealing with Idocs. To start with, you can give Orders01 in Basic types in WE60 selection screen and read out the details.
c. Once the partner profile is set up, there is a table called VOE4. This is the table where you can maintain the customer cross reference for incoming idocs.
d. Output type should be set up for EDI trigger (Tcode NACE) . You can use the existing programs. You can Check BA00 which is normally set up for EDI trigger as well. You can try triggering that first. You may get some errors at first. But do not panic. Just read those errors and then search the form for errors. You will get to know the next step.
e. Once you have the above settings, I think you are pretty much ready for EDI... you can try these. If you get struck in between, the form is there to help you...
Hope this helps...
Regards,
Mukund S

ALE : Error msg 'Application not posted'

Hello all,
when i send master data from sender to receiver then at recaiver side it shows the error like 'Application not posted'.
what it means ?
I have checked all the connection for both system.Remote connection is also working.IDOC generated at sender side is showing status 3. i.e. data is successfully transfered
whats the problem?
regards
Nilima

Hi Nilima,
Application not posted. error is for data integrity as already said.
Means that document can not be posted in recieving system. Say if you are sending a currency which is not configured in the recieving system. You are sending INR and recieving system needs USD say. So data can not be posted.
Try posting a document in the recieving system with the same data, it will through the same error take help of any functional consultant and solve the issue.
Now go to we05 and edit the idoc replicate the same changes as you already found. and reprocess the idoc using tcode BD87.
Hope this answers your curiosity,
Award points if useful revert otherwise,
Aleem.

Error when run Depreciation Posting Run AFAB

Hi,
I found error when run Depreciation Posting Run for period 7 2007.
FYI. I had run Unplanned Depreciation (TCode: ABAA) with document date 31.10.2007 and posting date 31.10.2007, trans. type 640. After that, i want to run Depreciation Posting Run (TCode: AFAB) with fiscal year: 2008, posting period: 7, reason for posting run: repeat. Select on Test Run. Then i found error message as below.
Error Message:
Documents manually posted within dep.doc.number range
Message no. AA728
Diagnosis
In the number range interval for the document type for posting depreciation, a document has been posted which was not created within the framework of depreciation posting. The last document posted by depreciation posting was assigned the number .
Procedure
Contact your Systems Specialist. When changing the number range interval for the document type in depreciation posting, you have to specify a new interval in which no documents exist. Using organizational measures, you can guarantee that there are no documents apart from those created by depreciation posting in this number range.
Can any one help how to solve this issue?

Hi Paul,
Now I go to TCode: FBN1 - Accounting Document Number Ranges, then i want to change the range for year 2008.
No Year From No          To No           Current No          Ext
03 2001   0300000000   0399999999   -                          /
03 2002   0300000000   0399999999   -                          /
03 2003   0300000000   0399999999   -                          /
03 2004   0300000000   0399999999   -                          /
03 2005   0300000000   0399999999   -                          /
03 2006   0300000000   0399999999   -                          /
03 2007   0300000000   0399999999   -                          /
03 2008   0300000000   0399999999   -                          /
03 2009   0300000000   0399999999   -                          /
Referring back to Asset Accounting, the Reference Document: 19.
Do it mean that my FI doc. no is 0300000019 ? I bit confuse on this..
Can you guide me more details on it?
Thanks in advance.
Edited by: Nur Aman Abdul Manap on Apr 15, 2009 2:09 AM

Someone can help me here with posting period error in doing GR post in SAP

Hi Seniors,
I've been getting below error while doing GR post. could someone help me to step on further with this error.
"Check table T001B for record type "0", the selected company code, account type S and G/L account 191*** If required, make sure that an entry is made in the table or an interval is changed."
i'm using test system as am a student of SAP MM.
Thank you very much..
Shivakumar

Open and Close Posting Periods
In this activity, you can specify which periods are open for posting for each variant. You have two time intervals (time period 1 and time period 2). In each interval, specify a period lower limit, a period upper limit, and the fiscal year.
You close a period by selecting the period specifications so that the period to be closed does not fall within them.
You can also assign authorization groups for permitted posting periods. This means that in month-end or year-end closing for example, you can open some posting periods for specific users only. The authorization group only has an effect on time period 1. The authorization object is F_BKPF_BUP (Accounting document: Authorizations for posting periods). For more information about assigning authorizations, see the corresponding section for User Maintenance.
Note
Specify G/L account numbers for your specifications. You define the permitted posting periods for the subledger accounting accounts using the relevant reconciliation accounts. To do this, specify the account type for the subledger accounting, such as D or K, and the relevant reconciliation account.
Caution
There must be a minimum entry for each variant. This entry must have + in column K, and the columns From Account and To Account must not contain entries. In the columns for the posting periods, specify the periods you want to always be open in this variant. With further entries, you define more specifically which periods are to be open for which accounts.
Activities
1. Specify the periods permitted for posting.
2. First enter the periods permitted for posting for all variants (minimum entry).
3. Then add entries for account types or account areas if the periods are to be further restricted for specific accounts.
4. In addition, enter an authorization group for each time period 1 in order to limit user access.

Error in PRRW because posting to CO-PA is required

Similar Messages

Maybe you are looking for