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

Similar Messages

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

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.

Standard cost estimate could not be found for the material

Dear All,
We have 4 manufacturing plants and 30 sale depots. We are maintaining price control (S) for FG and SFG in Manufacturing plants,price control (V) at depots for the same material code. we are getting an error message " standard cost estimate could not be found for the material" while doing billing at depot.
Please give me suggestion.
Your suggestion should be appreciate.
Thanks in advance............
AND
My client want to see profitability at manufacturing plant level and need break up for the COGM. So how can i get the values of depot sales.
please let me know how to do........

Hai
Price control should be S for Depot also. You need to run standard cost estimate in DEPOT after entering additive cost under CK74N for frieght, excise duty etc. To transfer the standard cost from the source plant you need to make configuration in OMD9 defining the receiver and sender combination so that system can pick up the cost from source plant. This special produrement type needs to be asigned in the material masters of DEPOT under MRP 2 view.
Pushkala

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

"The Destination Directory Could Not Be Determined For Photo Delluxe 4.0"

I Downloaded Adobes Photoshop from thier Site.
When trying to install pdx401upus.exe,
it will open up the Installation Wizard and then I get the Following "Warning" Message....
"The Destination Directory Could Not Be Determined For Photo Delluxe 4.0"
it just gives me a box to check that says "OK", and then the Wizard Shuts down.
Im running an HP Computer with Windows 7, Tons of HD Space, Ram, Memory ect.
I love using Adobe Photoshop, but since I got this new computer,
my Adobe Photoshop install disc seemed to be too old (Windows 95),
and therefore would not load to my new Computer/Operating System.
Any pointers, Websites, Instructions would be greatly appreciated.
Although I'm not a "Computer Dummy" I know just enough to get me into trouble, so the simpler the instructions....the better.

I am sorry Wwotr but I have not observed a user who has successfully installed and used Photo Deluxe on Windows 7. Since Photo Deluxe we have released 10 versions of Photoshop Elements. I would recommend utilizing the trial of Photoshop Elements 10 and seeing if that will fullfill your needs. You can find more information at http://www.adobe.com/products/photoshop-elements.html.

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

The Organizational Data could not be determined. Inform system admin

Hello All,
I am able approve PO from EBP, but getting this error 'The Organizational Data could not be determined. Inform system admin' when trying to appove PO from Universal Work List (portal) or when I try to open the work item via Busines Workplace (SAP GUI). Can anybody tell me if there is any config missing? or any suggestions to resolve this issue.
Any kind of help appreciated and rewarded.
Thanks,
Shekar

Hi Chandra,
Please check the Purchasing Organization and Purchasing Group in PO if they are not populated then this error is triggered. Please also check the user settings whether Purchasing organization information is maintained or not.
Regards,
Ravi G

Withholding tax -number could not be determined for numbering group ID0017

While positing the FB60 transaction with withholding tax for country Indonesia, the below error is coming:
A number could not be determined for numbering group ID0017
Message no. 7Q630
"The system could not determine a certificate number for the numbering
group.
Withholding tax types exist that are relevant to numbering. The system
cannot determine a certificate number because the Customizing settings
are incomplete.
Sysem Response
Payment cannot be made.
Procedure
Check the number ranges in the numbering group."
Already seen the wothholding tax number range and it is coorec. Please advise how to resolve.

Dear,
Please check whether you have assigned the number range to the number group in the below setting
Spro
Financial Account Global Setting> Withholding Tax> Extended Withholding Tax> Posting> India> Remittance Challan> Assign Number Range to Number Groups

Customer/vendor could not be determined for intermediate document

does any one know how to solve this problem, i got this error for an inbound idoc 820 (remmitance advice).

Hi rob,
Message no. FD017
This is the following message:
Customer/vendor could not be determined for intermediate document 0000000000047039
Message no. FD017
Diagnosis
Several procedures are defined for determining the partner (customer or vendor):
1. The customer/vendor can send his/her account number (the account
   number in our system) in the address segment.
2. The customer/vendor can send his/her account number (our number at
   the customer or vendor) in the address segment.
3. Only the name in the address segment clearly identifies the
   customer/vendor. In this case you can create an allocation within
   intermediate document customizing (IDoc base -> Control -> Forward
   inbound).
4. The customer/vendor is determined using his/her bank details (only
   for the "INVOIC01" intermediate document type).
5. The customer/vendor is taken from the control record of the
   intermediate document.
For 1.-3.: One of the address segments with the partner functions
           "II", "RS", "SU", 'SE' ("INV_ID01"), or "RS" or
           "LF" ("INVOIC01") is used for determining the
           customer/vendor.
Procedure
Create the customer or vendor within Financial Accounting or maintain his/her bank details.
Create customer         - Proceed
Customer bank details   - Proceed
Create vendor           - Proceed
Vendor bank details     - Proceed
If the customer/vendor can only be determined using his/her name, create a record within intermediate document customizing with
logical address = name, application = "FI" or "MM" and physical target in the SAP system = customer number/vendor number.
Proceed

Customer/vendor could not be determined for IDOC

Hi all,
Am trying to post incoming payments through EDI ..
IDOC Information
IDOC type: PEXR2002
Message type: REMADV
Function Module: IDOC_INPUT_REMADV
Process code: REMA
Am getting these 2 errors :
Customer/vendor could not be determined for intermediate document
Company code could not be determined for intermediate document
Has anyone encountered this problem, if yes can anyone suggest the solutions, any help regarding this is highly appreciated.
Thanks.

Hi,
Currently I am facing with the same type error when trying to post incoming payments through EDI.
IDOC Information
IDOC type: PEXR2002
Message type: REMADV
Function Module: IDOC_INPUT_REMADV
Process code: REMA
I am getting the below error:
1. Company code could not be determined for intermediate document
I have maintained record records for partner type and partner number in OBCA.
Please advice what are the other configuration changes do I need to maintain.
Your assistance would be highly appreciated.
Thanks.
Edited by: Victor Collins on Feb 27, 2009 9:31 PM

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)

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

Exchange 2010 - The certificate status could not be determined because the revocation check failed.

I have tried everything I have found online to get my DigiCert to work.
I have exported the cert and imported it into my child domains and they look perfect.
It is just my parent domain having issues.
netsh winhttp show proxy
does show my correct proxy server for http and https and port 8080
I have tried name, FQDN and IP address.
In the Bypass-list I have tried none, *.domain.com, and a list of all domains and child domains in my forest.
I have flushed the cache
certutil -urlcache crl delete
certutil -urlcache ocsp delete
and rebooted the Exchange 2010 (Windows 2008 R2) server
No matter what, I still see in my Server Configuration for the parent domain's DigiCert cert the message
The certificate status could not be determined because the revocation check failed.
with a red X on the left hand icon. Again, Child domains all say "The certificate is valid for Exchange Server usage."
Note: In spite of having the red X, I was able to assign via EMS the services.
Webmail works fine. Outlook Anywhere fails... I suspect it is due to my red X problem.
Suggestions?
Thanks in Advance
Jim.
Jim.

I have contacted DigiCert and they said the cert is working per their utility, hence the problem is outside the scope of their support.
I have followed, several times, http://support.microsoft.com/kb/979694
http://www.digicert.com/help/ reports all is well.
The DigiCertUtil.exe reports all is well and happy.
I have run
netsh winhttp set proxy proxy-server="http=myproxy:8080;https=myproxy:8080" bypass-list="*.mydomain.com"
Current WinHTTP proxy settings:
Proxy Server(s) : http=myproxy:8080;https=myproxy:8080
Bypass List : *.mydomain.com
I have flushed the cache using the commands
certutil -urlcache crl delete
certutil -urlcache ocsp delete
I still see in my Server Configuration for the parent domain's DigiCert cert the message
"The certificate status could not be determined because the revocation check failed."
with a red X on the left hand certificate icon.
To verify the cert via command line:
certutil -verify -urlfetch c:\mail_domain_com.cer
LoadCert(Cert) returned ASN1 bad tag value met. 0x8009310b (ASN: 267)
CertUtil: -verify command FAILED: 0x8009310b (ASN: 267)
CertUtil: ASN1 bad tag value met.
I suspect this is why I cannot get Outlook Anywhere to connect.
Child domains show a happy certificate icon. Parent domain does not.
Still scratching my head.
Thanks all!
Jim.

Shipping data could not be determined for the material

Similar Messages

Maybe you are looking for