Sponsored classes could not be determined; check grant

Hi Grants gurus,
I'm trying to create a budget document for a grant in T-CODE GM_CREATE_BUDGET, and the system issues the error "Sponsored classes could not be determined; check grant" message no. GRANTMGMT655.
Can anybody help me please??
Regards!!!

Hi Cesar,
Thank you very much for taking the time to answer my question, I try your suggestions with no success. At the end we noticed that the error was caused because the fund assigned to the grant in the dimensions tab was an internal fund. We changed it for an external fund and the error was solved.
Now I have a different error when I try to budget a grant with proposal status, as follows:
The GM Line amount in line 000001 is not equal to the total amount in Fiscal year distribution
Message no. GRANTMGMT490
Diagnosis
The amount in GM Line in line 000001 is incorrect in comparison with Fiscal year distribution.
System Response
The system sets an error status value.
Procedure
Check the entries in the Grants Management (GM) area of the screen (upper half) and the FM fiscal year distribution (lower half) and correct the values so that they match. You can do this in one of the following ways:
u2022 Adjust the values in both areas manually so that they match.
u2022 Adjust the values in the FM fiscal year distribution, then press Adjust from FM to GM. If you adjust the values in this part of the screen and then try to save without pressing this button, the message appears again.
With an awarded grant that error not appears. Have you any other suggestions?
Thank you in advance.
PD. up the Irons!

Similar Messages

EMC - Certificate status could not be determined because revocation check failed.

I've exhausted my resources on this issue and am reaching out for some assistance. I have setup Server 2008 R2 Enterprise SP1, running Exchange 2010 SP1. In EMC I have successfully imported a GoDaddy SSL certificate. Although I am receiving the message -
"The certificate status could not be determined because the revocation check failed."
Here are the steps I've taken to troubleshoot this so far:
[PS] C:\Users\Administrator\Desktop>netsh winhttp show proxy
Current WinHTTP proxy settings:
Direct access (no proxy server).
As you can see, direct access. Which is true, no proxy's on this network.
For good measure, I'll dump the urlcache.
certutil -urlcache ocsp delete
certutil -urlcache crl delete
Both return 0, reboot server.
Comes back up, same message in EMC.
From PS, I test exactly what its getting from GoDaddy.
[PS] C:\Users\Administrator\Desktop>certutil -f -urlfetch -verify mail.fluxlabs.net.crt
Issuer:
SERIALNUMBER=07969287
CN=Go Daddy Secure Certification Authority
OU=http://certificates.godaddy.com/repository
O=GoDaddy.com, Inc.
L=Scottsdale
S=Arizona
C=US
Subject:
CN=mail.fluxlabs.net
OU=Domain Control Validated
O=mail.fluxlabs.net
Cert Serial Number: 27b60918638e0d
dwFlags = CA_VERIFY_FLAGS_ALLOW_UNTRUSTED_ROOT (0x1)
dwFlags = CA_VERIFY_FLAGS_IGNORE_OFFLINE (0x2)
dwFlags = CA_VERIFY_FLAGS_FULL_CHAIN_REVOCATION (0x8)
dwFlags = CA_VERIFY_FLAGS_CONSOLE_TRACE (0x20000000)
dwFlags = CA_VERIFY_FLAGS_DUMP_CHAIN (0x40000000)
ChainFlags = CERT_CHAIN_REVOCATION_CHECK_CHAIN (0x20000000)
HCCE_LOCAL_MACHINE
CERT_CHAIN_POLICY_BASE
-------- CERT_CHAIN_CONTEXT --------
ChainContext.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
ChainContext.dwErrorStatus = CERT_TRUST_REVOCATION_STATUS_UNKNOWN (0x40)
ChainContext.dwErrorStatus = CERT_TRUST_IS_OFFLINE_REVOCATION (0x1000000)
SimpleChain.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
SimpleChain.dwErrorStatus = CERT_TRUST_REVOCATION_STATUS_UNKNOWN (0x40)
SimpleChain.dwErrorStatus = CERT_TRUST_IS_OFFLINE_REVOCATION (0x1000000)
CertContext[0][0]: dwInfoStatus=102 dwErrorStatus=1000040
Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=S
cottsdale, S=Arizona, C=US
NotBefore: 8/20/2011 7:49 PM
NotAfter: 8/20/2012 7:16 PM
Subject: CN=mail.fluxlabs.net, OU=Domain Control Validated, O=mail.fluxlabs.net
Serial: 27b60918638e0d
SubjectAltName: DNS Name=mail.fluxlabs.net, DNS Name=www.mail.fluxlabs.net
33 49 57 5d 6e d8 6b aa b9 61 73 95 44 07 c9 2e 55 6e 47 10
Element.dwInfoStatus = CERT_TRUST_HAS_KEY_MATCH_ISSUER (0x2)
Element.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
Element.dwErrorStatus = CERT_TRUST_REVOCATION_STATUS_UNKNOWN (0x40)
Element.dwErrorStatus = CERT_TRUST_IS_OFFLINE_REVOCATION (0x1000000)
---------------- Certificate AIA ----------------
Verified "Certificate (0)" Time: 4
[0.0] http://certificates.godaddy.com/repository/gd_intermediate.crt
---------------- Certificate CDP ----------------
Expired "Base CRL (05)" Time: 4
[0.0] http://crl.godaddy.com/gds1-55.crl
---------------- Base CRL CDP ----------------
No URLs "None" Time: 0
---------------- Certificate OCSP ----------------
Expired "OCSP" Time: 4
[0.0] http://ocsp.godaddy.com/
CRL (null):
Issuer: CN=Go Daddy Validation Authority, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
e5 53 19 6c 54 87 8c 62 23 1b b9 11 e1 d8 3d 3f b2 04 77 3f
Issuance[0] = 2.16.840.1.114413.1.7.23.1
Application[0] = 1.3.6.1.5.5.7.3.1 Server Authentication
Application[1] = 1.3.6.1.5.5.7.3.2 Client Authentication
CertContext[0][1]: dwInfoStatus=102 dwErrorStatus=0
Issuer: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US
NotBefore: 11/15/2006 8:54 PM
NotAfter: 11/15/2026 8:54 PM
Subject: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=
Scottsdale, S=Arizona, C=US
Serial: 0301
7c 46 56 c3 06 1f 7f 4c 0d 67 b3 19 a8 55 f6 0e bc 11 fc 44
Element.dwInfoStatus = CERT_TRUST_HAS_KEY_MATCH_ISSUER (0x2)
Element.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
---------------- Certificate AIA ----------------
No URLs "None" Time: 0
---------------- Certificate CDP ----------------
Verified "Base CRL" Time: 4
[0.0] http://certificates.godaddy.com/repository/gdroot.crl
---------------- Base CRL CDP ----------------
No URLs "None" Time: 0
---------------- Certificate OCSP ----------------
Expired "OCSP" Time: 4
[0.0] http://ocsp.godaddy.com
CRL (null):
Issuer: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US
da 1e d5 63 5c 05 58 50 4e db d2 4e e8 9d 28 9d c4 36 b3 1e
Application[0] = 1.3.6.1.5.5.7.3.1 Server Authentication
Application[1] = 1.3.6.1.5.5.7.3.2 Client Authentication
Application[2] = 1.3.6.1.5.5.7.3.4 Secure Email
Application[3] = 1.3.6.1.5.5.7.3.3 Code Signing
CertContext[0][2]: dwInfoStatus=109 dwErrorStatus=0
Issuer: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US
NotBefore: 6/29/2004 12:06 PM
NotAfter: 6/29/2034 12:06 PM
Subject: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US
Serial: 00
27 96 ba e6 3f 18 01 e2 77 26 1b a0 d7 77 70 02 8f 20 ee e4
Element.dwInfoStatus = CERT_TRUST_HAS_EXACT_MATCH_ISSUER (0x1)
Element.dwInfoStatus = CERT_TRUST_IS_SELF_SIGNED (0x8)
Element.dwInfoStatus = CERT_TRUST_HAS_PREFERRED_ISSUER (0x100)
---------------- Certificate AIA ----------------
No URLs "None" Time: 0
---------------- Certificate CDP ----------------
No URLs "None" Time: 0
---------------- Certificate OCSP ----------------
No URLs "None" Time: 0
Application[0] = 1.3.6.1.5.5.7.3.1 Server Authentication
Application[1] = 1.3.6.1.5.5.7.3.2 Client Authentication
Application[2] = 1.3.6.1.5.5.7.3.4 Secure Email
Application[3] = 1.3.6.1.5.5.7.3.3 Code Signing
Exclude leaf cert:
b1 04 4b 90 a1 d3 48 de 46 bd d7 50 20 e3 44 b8 3f 68 39 f7
Full chain:
68 36 4d 37 2e 96 bd d2 aa 77 3f d0 e8 78 a9 e6 68 bd 7d 71
Verified Issuance Policies:
2.16.840.1.114413.1.7.23.1
Verified Application Policies:
1.3.6.1.5.5.7.3.1 Server Authentication
1.3.6.1.5.5.7.3.2 Client Authentication
Cert is an End Entity certificate
ERROR: Verifying leaf certificate revocation status returned The revocation function was unable to check revocation because the revocation server was
offline. 0x80092013 (-2146885613)
CertUtil: The revocation function was unable to check revocation because the revocation server was offline.
CertUtil: -verify command completed successfully.
As you can see, the "revocation server is offline."
So I run the same test from another server on the LAN.
Verified Issuance Policies:
2.16.840.1.114413.1.7.23.1
Verified Application Policies:
1.3.6.1.5.5.7.3.1 Server Authentication
1.3.6.1.5.5.7.3.2 Client Authentication
Cert is an End Entity certificate
Leaf certificate revocation check passed
CertUtil: -verify command completed successfully.
It passes. The server's firewall has been disabled. DNS cache has been cleared. I have verified everything I can, and still failing to verify.

[PS] C:\Users\Administrator\Desktop>Get-ExchangeCertificate |fl
AccessRules : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.Acces
trol.CryptoKeyAccessRule}
CertificateDomains : {mail.fluxlabs.net, www.mail.fluxlabs.net}
HasPrivateKey : True
IsSelfSigned : False
Issuer : SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy
, Inc.", L=Scottsdale, S=Arizona, C=US
NotAfter : 8/20/2012 7:16:57 PM
NotBefore : 8/20/2011 7:49:30 PM
PublicKeySize : 2048
RootCAType : ThirdParty
SerialNumber : 27B60918638E0D
Services : IMAP, POP, IIS, SMTP
Status : RevocationCheckFailure
Subject : CN=mail.fluxlabs.net, OU=Domain Control Validated, O=mail.fluxlabs.net
Thumbprint : 3349575D6ED86BAAB96173954407C92E556E4710
[PS] C:\Users\Administrator\Desktop>Enable-ExchangeCertificate -Thumbprint 3349575D6ED86BAAB96173954407C92E556E4710 -Services POP,IMAP,SMTP,IIS
The command has already been executed. Yes, I have seen those sites. Neither have worked. Like I said, it is directly connected; and no proxies are set.
-- Jeremy MCSpadden Flux Labs

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.

Po check error (Jurisdiction code could not be determined)

Hello everybody.
I am in SRM 5.0 and in Brazil we use jurisdiction code too, all notes for jurisdiction codes are applied and the calculation is occurring in R/3 in the moment of Po creations, the problem is that when the po are created and I need to display and check the PO the system displays an error message " JURISDICTION CODE COULD NOT BE DETERMINED" and aproval can't be done too.
Someone that uses jurisdiction code knows what could be done to solve.
Thanks
Nilson

Hi
<u>Please go through the following links -></u>
Jurisdiction code could not be determined - ECS
Re: Jurisdiction code could not be determined ?
Re: Tax jurisdiction in R/3
Jurisdiction code could not be determined
SUS - Jurisdiction Code not determined
Re: Tax code T1 does not exist for jurisdiction code error in shopping basket
Re: You are not allowed to enter a tax jurisdiction code for country US msg
Re: Tax Jurisdiction Error in SRM
Tax error while posting an invoice in SRM
Tax setting in Extended Classic Scenario
You are not allowed to enter a tax jurisdiction code for country US
Hope this will help.
Regards
- Atul

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

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

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

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)

"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

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.

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

<i>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</i>

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,

Business Place for document could not be determined

Hi,
When I am posting Remittance challan I am getting this following error,
"Business Place for document could not be determined".
Could any body please help me to solve this problem.
I maintained the following settings in system
1. T-Code: J_1IEWTNUMGR
UN04 SC04 194C 02
2. T-Code: J_1IEWTNUM
02 02
3. T-Code: J_1IEWTNO
Maintained Number ranges
I posted vendor document and I gave Business place and Section code also. Even After all the settings I am getting this problem. Please let me know is there any steps I missed are any thing I have to maintain in system.
Best Regards
Raj

Hi Pavan,
Thanks for you replay. I checked in table, data available in the table J_1IEWTNUMGR against Company code, Business place and Off Key.
One more question is whether we need to give Business place or Section code while creating TDS challan using J1INCHLN. It will appear like "Business Place/Section Code" in the screen. If I select from drop down It is taking Section code. Is it possible to change the logic from Section code to Business place.
Thanks & Regards
Raju.

The attributes for user could not be determined --

Hi,
Our is extended classic scenario:srm5.0 & ECC6.0
we are getting the following error in the org plan:
"The attributes for user could not be determined "
The error is occuring , when we log into the web browser.
we also have a error in the org plan, under the user at the check tab,"No attribute found for scenario BBP".
when we run the BBP_ATTR_CHECK & BBP_BP_OM_Integrate, we have no errors...
Thanks in advance,
RK.

Hi All,
Thanks for your support...
I check the T-code:BBP_ATTR_CHECK & BBP_BP_OM_INTEGRATE.
I also checked the attributes for the CP are ok,still i had the error appearing in the WEB.
The solution:
The CP has been deleted from the org plan.
Once again,we generated the users from USERS_GEN and assign CP to the org plan again at the same.Now the Attributes error is gone.... and the issue is resolved.
Thanks and Regards,
RK.

Sponsored classes could not be determined; check grant

Similar Messages

Maybe you are looking for