Error "codepage could not be determined for the receiver-system"

Hi,
we use the idoc-adapter to send message from mySAP ERP to PI.
All worked fine.
So, this morning I have changed the datatype of the messageId from "char" to "int" in mySAP ERP in the customizing menue (install param). So, no message received in SAP PI.
When I start transction "we05" in mySAPERP" I get the following error:
"codepage could not be determined for the receiver-system" status 02.
I have changed the datatyp to "char" but the same probleme
Can anybody help me please?
Regards
Stefan

This error shouldn't occur unless there is some modification at the OS level codepages.
Please check the entried in the RFC destination for connecting to the XI system. Unicode settings.
Regards,
Prateek

Similar Messages

IDoc type could not be determined for the IDoc

I am trying to Post the payment run through the transaction F110.
In the payment run log i get the following message:
"IDoc type could not be determined for the IDoc"
But in fact the IDoc is generated and it is displayed in We05.
I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
Has anybody Idea about why this error is coming and how i can resolve this?
This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
Would appreciate if anyone can please help on the same.
Thanks & Regards,
Narayanan

Hi,
If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
still if you are having any problem
Check in the below path:
IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
2. Assign Release Approval Procedure for Release for Payment
3. Define Users with Authorization to Payment Release
Thanks
Chandra

IDoc type could not be determined for the IDoc in F110

Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
Regards

If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

Getting error "Codepage could not be determined" in background job

Hello Friends,
I am running a background job with a variant and the job get cancelled with the following error message.
Codepage could not be determined
Message no. FES025
Please give your valuable comments.
Thanks,
Senthil

Hi,
Check the oss note 765763(Setting the upload/download codepage for a SAPGUI connection) released for this purpose, as per the documentation of this note, you need to modify the standard program LSFESF03 in order to get rid of this error,
Also check the note 882961(File download: codepage conversion error FES024)
Hope this helps,
Rgds,

BDC Error - Codepage could not be determined

Hello Gurus,
We are having a problem with BDC in transaction VF01.
The return message is FES-025 "Codepage could not be determined".
First of all the details and what have been done so far:
- The funcion module with BDC is called by an EDI message that is send on the creation of the SD Invoice.
- In Online mode, no errors are raised;
- The errors are only raised when the program runs in background - Manual processing of EDI message via T-Code WE19 (online mode) runs with no problems;
- In DEV enviroment, everything runs smoothly (both online and background modes) and we achieve the required result;
- In QAS enviroment, with exacly the same versions of code, the background process fails;
- Both DEV and QAS work on the same physical machine, on different instances.
I've searched quite a lot about this error and most results talk about the usage/call of GUI_UPLOAD or GUI_DOWNLOAD. We are NOT using this type of funcions in our code (or something that would connect to the client).
Any ideias?
Thanks in advance, best regards,
João Argêncio

Some additional informations:
- The sistem is non-unicode;
- The EDI message source and destination are the same machine (inter-company process);
- The user assiciated in IDoc Config has SAP_ALL privileges;
- Both systems are in the same release levels (ECC 5);
- All IDoc configuration is equal in both DEV and QAS instances.
If you need any additional information just let me know.
Thanks oin advance, best regards,
João Argêncio

Getting an error "Customer could not be determined" for IDOCs in SCM 7.0

Hi Friends,
I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
I have noticed that 2 things .
1. E1ADRE1 field is NOT being sent by the ECC system .
2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
Has anybody faced this problem before ?
I look forward to replies.
Detailed error is given below.
Regards,
Ranjini.
Customer could not be determined
Message no. /SAPAPO/EDI010
Diagnosis
The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
The section was not available in the processed IDoc.
System Response
The system cancels processing.
Procedure
Configure the EDI convertor in such a way that the corresponding section has a value.

Hi Ranjini,
Please look into the following
1) Customer master data is fully maintained
2) Customer number ranges are fully defined in customisation
3) Customer address details are maintained
4) Is there any special characters used while defining customer data or customer
number like $, #,[ etc.,?
5) Customer int models are active in SCM side prior to IDOC processing (including
customer, demand, stocks etc)
Please confirm your findings
Regards
R. Senthil Mareeswaran.

Shipping data could not be determined for the material

hi all,
while creating STOs for i get a message that shipping data for the material canoot be determined for the material. the plants are maintained as customers. the shipping tab in item detail in STO order is not appearing. the shipping point is getting dertmined for sales orders from the same plant and material. am also able to ceate STOs between other pair of plants.
thnx in advance
saurabh
Message was edited by:
saurabh diwakar

Hi,
Shipping point is determined by "shipping conditions" + "loading group" + "plant".
Shipping conditions are fetched from customer master / or if maintained in the sales doument type they are fetched from there.
Loading group fetched from material master.
Plant fetched from CMIR / CMR / MMR.
You do the shipping point determination using the transaction code "OVL2" If SC or LG or PLANT are deviating from the entries in the customer or material master then also you will not get the shipping point.
Reward points if solution helps.
Regards,
Allabaqsh G. Patil

BGD Job : Codepage could not be determined

Hi all,
    I run a report (YMMI0038) in background and hitting the following error :
    Codepage could not be determined FES 025 E
    Job cancelled after system exception ERROR_MESSAGE 00 564 A
    This has no problem when running in foreground.
    Do you have any idea for this ?
Best Regards,
Ken

Hello Ken,
Please check -
Note 765763 Setting the upload/download codepage for a SAPGUI connection
Note 882961 File download: codepage conversion error FES024
Thanks

Company code could not be determined for IDoc #.......

I was trying to generate an IDoc manually by using the tcode WE19. I have manually keyed the data in to the respective segments for the basic type PEXR2002 and message type REMADV. After this while processing, the IDoc is getting generated, but not posted OK. I am getting the following two error messages 51 stating:
'Company code could not be determined for the IDoc #....'
'Customer/vendor could not be determined for the IDoc #.'
Can any one give some inputs on this issue?
Shaji
Message was edited by: Shaji Thomas

Hi Shaji,
You may look at the OSS note 316811.
Thanks
Vinod

Currency could not be determined for person ?

Hi,
I have created in PA30 the "compensation process" subtype " Spot bonus" for an employee , but then when i changed the status in ECM ( Enterprise compensation management) ( From In planning -> Approved ,( OK) , Approved to " Active" I got the following error"
"Currency could not be determined for person Nguyen Ngoc Ngan between 30.10.2007 and 30.10.2007"
Please help me out with this
Thank you very much

Great Suresh , You are excellent !
I have added a new record in the table T500C for my local currency i have tested successfully .
But i face a small problem with " Salary adjustment" when i created in compensation process infotype the salary adjustment ( In planning ) it is ok , but when i change the status from "Approved to active " I got the following err ;
"Salary adjustment of Nguyen Ngoc Ngan on 31.10.2007 could not be activated "
( Bonus worked fine ).
Thanks

Error:The grouping element could not be determined for project

Hi,
When I am trying to issue goods for a project,I am getting the following error
"The grouping element could not be determined for project 1., plant 2., and MRP group 3.."
what may be the reason for this reason.
Regards,
Raju

Hi,
You are using Automatic Requirement Grouping in your project and there is some issue with the Material Master,please check the Material Master Views.
Muzamil

PY error message - EE's salary group could not be determined for Plan Life

We are running through Payroll errors when there is a Separation action being carried :
u201DEmployeeu2019s salary group could not be determined for plan LIFEu201D.
On IT0168 the costs are u20180u2019
This has to be resolved ASAP. Any inputs/ advise is greatly appreciated.

During the "Separation" action, does the employee change WT on IT0008?
If so, it could be that the Life Plan's Calculation Base does not include that WT (and check the IMG under Payroll > Benefits Integration > Define WageTypes for Benefit Plans)

Error: FES025. Codepage could not be determined

Hi,
I have a number of programs that run using an include containing the function GUI_DOWNLOAD to create files lacally or on the server. The programs work perfectly in foreground but their purpose is to run as jobs every night and create the files on the server, which returns the job as CANCELLED and the log reads;
11.12.2008 09:00:17 No se ha podido determinar code page (Codepage could not be determined)
11.12.2008 09:00:17 El job ha sido cancelado tras excepción de sistema ERROR_MESSAGE.
When I execute the program in foreground using a message log I recieve a message on the status bar indicating;
Transfered 913 bytes, code page 1160.
I'm not quite sure what the code page does. I read another forum which explained that it has something to do with the character set.
Is there any way can assign the code page myself in the program?
Regards,
Simon

OPEN DATASET gv_file FOR INPUT IN TEXT MODE ENCODING DEFAULT
                            WITH SMART LINEFEED.
ENDIF.
*If the Presentation Server is selected on the selection screen
IF p_local EQ gc_x.
    LOOP AT gt_text_file INTO wa_text_file.
      CLEAR wa_text_table.
      SPLIT wa_text_file-line AT gc_comma INTO   wa_text_table-objectid
                                                  wa_text_table-lifnr
                                                  wa_text_table-matnr
                                                  wa_text_table-ebelp
                                                  wa_text_table-tdname
                                                  wa_text_table-spras
                                                  wa_text_table-textid
                                                  wa_text_table-object
                                                  wa_text_table-line.
      APPEND wa_text_table TO gt_text_table.
    CLOSE DATASET gv_file.

COREid Federation Error: A local user session could not be created for the

Hi,
I installed two instances of COREid Federation in my machine. Also installed SiteMinder and LDAP. Source Domain of COREid (8101) uses LDAP as IdMBridge and Destination Domain (9101) uses SiteMinder as IdMBridge. I am trying to access the resource protected by the SiteMinder from the source domain using the URL which is constructed using the pattern given in the PDF:
http://mymachine.domain.com:8101/shareid/saml/ObSAMLTransferService?DOMAIN=DestinationDomain&method=POST&TARGET=http://mymachine.domain.com:8887/Source/Source.html
Assertions are generated and I can see the assertion in the Source domain and transferred to the Destination Domain.
I get the following error in the Destination Domain Shareid Log file:
ERROR - [http10113-Processor3] - RECEIVER: ERROR: A local user session could not be created for the assertion
Please help me to solve this issue?
Note: The Web agent runs on the web server instance 8887.
SiteMinder is able to protect the resource when accessed.

Typically that error occurs when the destinations access management system can't find the user based on the SAML attribute. Check to make sure that the attribute that you are matching on matches exactly.

Error "codepage could not be determined for the receiver-system"

Similar Messages

Maybe you are looking for