Payroll period does not correspond to master data error in INLK run & soln

Dear All,
Just wanted to share this Issue and solution which i found after debugging.
I am not sure it is 100% correct.
I am working on indian payroll and was doing lagacy data transfer with INLK schema
i was used to get error '2 payroll period does not correspond to master data'
and this was for only new joinees in that period .what i found out after debugging is
for e.g. employee is hired in 03.06.2011 .and record in t558b is
90300035 1 2011 1 2011 3 01.06.2011 31.06.2011
where 01.06.2011 is a for period begin date ,
now in payroll program this is being checked with joining date in following subroutine check_aper_versus_t558b
so it ends up with above error.now if i go and change 01.06.2011 to 03.06.2011 in T558B then payroll will be successful.
I dont no whether this is right approach but this removed that error.Just wanted to share so
It might help the members.

la diferencia es la fecha del campo FPBEG que debe ser la fecha para los empleados que no esten con el año o periodo completo
the difference is the date field FPBEG Table T558B to be the date for employees who are not full with the year or period

Similar Messages

Object in import-file header does not correspond to the migration object

Hi Forum,
I have loaded Business partner successfully with the file created in Workbench with test data.
Now I want to load the data from Application server. But i am getting the error
"Object in import-file header does not correspond to the migration object".
I have read that the import file should have 3 types of record
1. Header record corrs to the structure TEMINFO
2. Actual data records
3. Final record for individual object.
I am not sure where I am making a mistake
my files header looks like
<004F><Space><&INFO><Company><Migration Object><User><Date><Time>
Please help.
Thanks in advance

I am assuming you are in transaction EMIGIMP loading a converted migration file for import, correct?
If so, you should be able to read the company, mig. object, user name, etc. in the import file tab overview. If conversion did not work correctly, this info will not display here.
It is possible you are missing some data in the header, or spacing is not correct. Are you converting the input file with program REMIG_FILE_TRANSFORM or are you trying to create the migration file yourself?

In FB60, duplicate invoice check does not work if invoice date is different

In FB60, duplicate invoice check does not work if invoice date is different
This issue is in FB60 and not MIRO.
Duplicate invoice check is activated in vendor master.
I posted an invoice for a vendor with amount $ 100, Reference 1234 Invoice date Nov 01, 2011
I tried posting for same vendor (and also Co Code) with amount $ 100, Reference 1234 Invoice date Nov 01, 2011. System does not allow. This is fine.
Now I change only date, from Nov 01 to Nov 02, and system allow posting.
Why I don't get the error message when date is different ? It should not be treated as a different invoice since invoice reference, amount, Vendor and Co Codes are same.
SAP documentation says that it checks document date during duplicate invoice check even for FI invoices, then why does it allows in this case.
Is this a bug ?
I already tried changing settings in SPRO under LIV, this does not impact FB60 invoice booking.
Thanks
Sandeep

Hi,
Use BTE - 1110 - (Check on Invoice Duplication) for FB60. Take the help of your ABAPer to make a coding in Function module mentioned in BTE.
Need to make a copy of the FM and then you can do relevant coding.
refer the link.
[http://www.thesapconsultant.com/2006/10/sap-business-transaction-events.html]
Regards,
Shridhar

Field 'Contract Period' does not exist in definition for business component

Hi everyone
I create a Field "Contract Period" in BC "Quote" with an extended table and put it in the applet view "Quote Full Form Applet" the field works fine in the view, we can update and insert information in it and shows perfect in the database also.
Our problem is when create a Integration Object for reports in BIP Reports the system said something like this when we try to generate the sample data:
ObjMgrLog     Error     1     0000002d4cd016bc:0     2010-11-02 13:18:39     (adptutils.cpp (5715)) SBL-EAI-04376: Method 'FieldValue' of business component 'Quote' (integration component 'Quote Template') returned the following error:
"Field 'Contract Period' does not exist in definition for business component 'Quote'.
We compiled the BC and the IC, and did the Deployment of the IC in Tools but it didn't work, the thing here is if I remove this field the report works fine. Is there any other component or Object that we have to compile to get Siebel recognition?
Any ideas?
Thanks in advance
Edited by: user7286211 on Nov 2, 2010 8:05 PM

To do the same change with the transaccion FB02 y FB03, create an enhancemente point in the program: SAPMF05L dynpro: 1301, module: DYNPRO_MODIFIKATION, at the of perform open_fi_dynpro_mod and write:
LOOP AT SCREEN.
IF sy-tcode = 'FB02'.
    IF screen-name = 'BSEG-HKTID'.
      screen-input = 1.
      screen-invisible = 0.
      screen-active = 1.
      screen-output = 1.
      screen-group4 = ' '.
      MODIFY SCREEN.
      EXIT.
    ENDIF.
elseif sy-tcode = 'FB03'.
      IF screen-name = 'BSEG-HKTID'.
      screen-input = 0.
      screen-invisible = 0.
      screen-active = 1.
      screen-output = 1.
      screen-group4 = ' '.
      MODIFY SCREEN.
      EXIT.
    ENDIF.
endif.
ENDLOOP.
and, all ready.

Error – SAML Single Logout request does not correspond to the logged-in session participant

We are relatively new to ADFS, having set up working rp-trusts with three partners in the last few months. Our 4th partner is proving problematic. Single sign in works, but the ADFS
responds the single logout request from the RP with a status of Requester. The ADFS event log shows
The SAML Single Logout request does not correspond to the logged-in session participant.
Requestor: https://test-sso.rp.com/fed/sp
Request name identifier: Format: urn:oasis:names:tc:SAML:2.0:nameid-format:persistent, NameQualifier: http://fs.idp.com/adfs/services/trust SPNameQualifier:
https://test-sso.rp.com/fed/sp, SPProvidedId:
Logged-in session participants:
Count: 1, [Issuer: https://test-sso.crmondemand.com/fed/sp, NameID: (Format: , NameQualifier:
SPNameQualifier: , SPProvidedId: )]
This request failed.
User Action
Verify that the claim provider trust or the relying party trust configuration is up to date. If the name identifier in the request is different from the name identifier
in the session only by NameQualifier or SPNameQualifier, check and correct the name identifier policy issuance rule using the AD FS 2.0 Management snap-in.
The LogoutRequest looks like this
<samlp:LogoutRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
Destination="https://fs.timken.com/adfs/ls/"
                ID="id-HAScmHCfwfuYk76bce6YBfO2uOM-"
IssueInstant="2013-01-14T13:24:04Z"
Version="2.0">
. . . cert, etc. omitted . . .
<saml:NameID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
NameQualifier="http://fs.idp.com/adfs/services/trust"
SPNameQualifier="https://test-sso.rp.com/fed/sp"
>jsmith</saml:NameID>
<samlp:SessionIndex>_df13d31b-162e-42e1-8331-f36be6bf1194</samlp:SessionIndex>
</samlp:LogoutRequest>
The session index and the username in NameID matches the Response we got from our AuthRequest. I don't know how to figure out what ADFS thinks does not match.
Any suggestions would be appreciated.
For completeness sake, the Response to AuthRequest looked like this.
<Subject>
            <NameID>jsmith</NameID>
            <SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">
                <SubjectConfirmationData NotOnOrAfter="2013-01-14T13:28:52.199Z"
                                         Recipient="https://test-sso.rp.com/fed/sp/authnResponse20"
                                         />
            </SubjectConfirmation>
        </Subject>
        <Conditions NotBefore="2013-01-14T13:23:52.183Z"
                    NotOnOrAfter="2013-01-14T14:23:52.183Z"
                    >
            <AudienceRestriction>
                <Audience>https://test-sso.rp.com/fed/sp</Audience>
            </AudienceRestriction>
        </Conditions>
        <AuthnStatement AuthnInstant="2013-01-14T13:10:43.826Z"
                        SessionIndex="_df13d31b-162e-42e1-8331-f36be6bf1194"
>

Okay, here are the relevant SAML messages.
The <AuthnRequest>
<samlp:AuthnRequest ID="_ced78e65-14d2-4c4d-8417-51f664a9e2e3"
                    Version="2.0"
                    IssueInstant="2013-02-04T13:29:20.887Z"
                    Destination="https://fs.timken.com/adfs/ls/"
                    Consent="urn:oasis:names:tc:SAML:2.0:consent:unspecified"
                    xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
                    >
    <Issuer xmlns="urn:oasis:names:tc:SAML:2.0:assertion">http://fs.timken.com/adfs/services/trust</Issuer>
    <Conditions xmlns="urn:oasis:names:tc:SAML:2.0:assertion">
        <AudienceRestriction>
            <Audience>https://test-sso.salesdemand.com/fed/sp</Audience>
        </AudienceRestriction>
    </Conditions>
</samlp:AuthnRequest>The AuthnRequest Response<samlp:Response ID="_890f3128-6cae-414e-8272-30cde3bda94a"               Version="2.0"                IssueInstant="2013-02-04T13:29:29.748Z"                Destination="https://test-sso.salesdemand.com/fed/sp/authnResponse20"                Consent="urn:oasis:names:tc:SAML:2.0:consent:unspecified"                xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"                >    <Issuer xmlns="urn:oasis:names:tc:SAML:2.0:assertion">http://fs.timken.com/adfs/services/trust</Issuer>    <samlp:Status>        <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success" />    </samlp:Status>    <Assertion ID="_82f82c5c-2653-4e18-9308-349ebeb67743"               IssueInstant="2013-02-04T13:29:29.748Z"               Version="2.0"               xmlns="urn:oasis:names:tc:SAML:2.0:assertion"               >        <Issuer>http://fs.timken.com/adfs/services/trust</Issuer>        <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">            <ds:SignedInfo>                <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />                <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />                <ds:Reference URI="#_82f82c5c-2653-4e18-9308-349ebeb67743">                    <ds:Transforms>                        <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />                        <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />                    </ds:Transforms>                    <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />                    <ds:DigestValue>RxZZLlbdh5eD6Ht4+aVna3Rtbnc=</ds:DigestValue>                </ds:Reference>            </ds:SignedInfo>            <ds:SignatureValue>Es8LAN9noqGIJEbgZe/...XW8LAv5Mgr3tOXpHRlcsJNss/A==</ds:SignatureValue>            <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">                <ds:X509Data>                    <ds:X509Certificate>MIIFDDCCA/SgAwIB...</ds:X509Certificate>                </ds:X509Data>           </KeyInfo>        </ds:Signature>        <Subject>            <NameID>mooreta</NameID>            <SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">                <SubjectConfirmationData NotOnOrAfter="2013-02-04T13:34:29.748Z"                                         Recipient="https://test-sso.salesdemand.com/fed/sp/authnResponse20"                                         />            </SubjectConfirmation>        </Subject>        <Conditions NotBefore="2013-02-04T13:29:29.732Z"                    NotOnOrAfter="2013-02-04T14:29:29.732Z"                    >            <AudienceRestriction>                <Audience>https://test-sso.salesdemand.com/fed/sp</Audience>            </AudienceRestriction>        </Conditions>       <AuthnStatement AuthnInstant="2013-02-04T13:29:29.545Z"                        SessionIndex="_82f82c5c-2653-4e18-9308-349ebeb67743"                        >            <AuthnContext>                <AuthnContextClassRef>urn:federation:authentication:windows</AuthnContextClassRef>            </AuthnContext>        </AuthnStatement>    </Assertion></samlp:Response>The LogoutRequest<samlp:LogoutRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"                     Destination="https://fs.timken.com/adfs/ls/"                     ID="id-uvoTioVCLdMycE88o-6CU5RrSNM-"                     IssueInstant="2013-02-04T13:29:57Z"                     Version="2.0"                     >    <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"                 Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity"                 >https://test-sso.salesdemand.com/fed/sp</saml:Issuer>    <dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">        <dsig:SignedInfo>            <dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />            <dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />            <dsig:Reference URI="#id-uvoTioVCLdMycE88o-6CU5RrSNM-">                <dsig:Transforms>                    <dsig:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />                    <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />                </dsig:Transforms>                <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />                <dsig:DigestValue>ZT0yQqiaL2dD2a7rt6ywJ9EoM1I=</dsig:DigestValue>            </dsig:Reference>        </dsig:SignedInfo>        <dsig:SignatureValue>Z7F7zYS31y1K48FbUHevJT86+txOlPM9awlHiMNj1TiMxRAEVz1rOj2uG0oVMd7NkblkneCrE8aVtJuebdUY4Q0DAcXR8lSTuNEFocT2R6eCIwQb48xQqQMs8ZE6siPsPFMS+QAhpgDom/IY61L/.../NNxVg==</dsig:SignatureValue>        <dsig:KeyInfo>            <dsig:X509Data>                <dsig:X509Certificate>MIIFxTCCBK2gAwIBAgIQAN+.../G6p95pNm1ZAqroUjufLeHO4q34Mx3xNyw0tmyjmWgkxY11Pa+M0gCeLOdLzxafIOXUFXOhKfOUg4Jp4S+/sCVcd9fBDPvfEHSr8uMmQC2IdQaRE7IvZdRF0OUP+l1MpRBkMsy98hPXTBK6n1ivklOxzmWie88jav8gzjWhwQC5Ia2/JNYxVBkPsNkRw86n8KBnlsumU9EV0dAeXTOaehKtG+RNnD1Gt4Y34TQccaIbf7OTLisY4kMkjZbRu3sJnX9KjM=</dsig:X509Certificate>            </dsig:X509Data>        </dsig:KeyInfo>    </dsig:Signature>    <saml:NameID xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"                 Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"                 NameQualifier="http://fs.timken.com/adfs/services/trust"                 SPNameQualifier="https://test-sso.salesdemand.com/fed/sp"                 >mooreta</saml:NameID>    <samlp:SessionIndex>_82f82c5c-2653-4e18-9308-349ebeb67743</samlp:SessionIndex></samlp:LogoutRequest>The LogoutRequest Response<samlp:LogoutResponse ID="_bf7199a8-3248-4201-9ca4-609bec5404d6"                      Version="2.0"                      IssueInstant="2013-02-04T13:29:59.076Z"                      Destination="https://test-sso.salesdemand.com/fed/sp/samlv20"                      Consent="urn:oasis:names:tc:SAML:2.0:consent:unspecified"                      InResponseTo="id-uvoTioVCLdMycE88o-6CU5RrSNM-"                      xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"                      >    <Issuer xmlns="urn:oasis:names:tc:SAML:2.0:assertion">http://fs.timken.com/adfs/services/trust</Issuer>    <samlp:Status>        <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Requester" />    </samlp:Status></samlp:LogoutResponse>The ADFS Error Log EntryThe SAML Single Logout request does not correspond to the logged-in session participant. Requestor: https://test-sso.salesdemand.com/fed/sp Request name identifier: Format: urn:oasis:names:tc:SAML:2.0:nameid-format:persistent, NameQualifier: http://fs.timken.com/adfs/services/trust SPNameQualifier: https://test-sso.salesdemand.com/fed/sp, SPProvidedId: Logged-in session participants: Count: 1, [Issuer: https://test-sso.salesdemand.com/fed/sp, NameID: (Format: , NameQualifier: SPNameQualifier: , SPProvidedId: )] This request failed. User Action Verify that the claim provider trust or the relying party trust configuration is up to date. If the name identifier in the request is different from the name identifier in the session only by NameQualifier or SPNameQualifier, check and correct the name identifier policy issuance rule using the AD FS 2.0 Management snap-in.

Enprise JC error: series period does not match current period

I want to make create invoice from Enprise Job Costing Contract. There are some lines in Contract Detail but I want to process only two of them. I put the amount in Invoice Now, Post Date, and Invoice Due Date.
The invoice is supposed to be from previous posting period (the previous month/year) so I search the correct series number in Invoice No. drop-down list in the Job Costing Contract form. But the available options are only manual and serial number of current period. If I click Process Invoice Now button, I get error message: Error creating invoice: series period does not match current period
I tried to change the settings from Administration > System Initialization > Document Numbering to set the numbering series to previous period but so far nothing changed, and I still can not create invoice.
I currently use SAP B1 8.8 PL 13 and Enprise Job Costing 8.8 (version 8.80.101)
Anybody can help me? Thank you in advance for any good advice.

Hi Sandy,
your SAP support partner will be able to register a ticket on the Enprise Support Portal to have this investigated for you, Enprise do not answer questions directly from this forum.
Having said that... it sounds as though the invoice numbering series you are trying to use is only valid for a specific year. Did you make sure you also changed the Invoice Date (top right side of screen) to be in the same year?
kind regards,
Cathy

Copy opening does not clear the destination data - Just appends

Hi All,
Copy opening does not clear the destination data. It just appends so if i run the copy opening package twice i can see the signed data get doubled.
We have SAP BPC NW 7.5 SP08 Patch 1001.
I working on the Periodic Application.
Copy opening Script logic:
*FOR %TIME% = %TIME_SET%
*RUN_PROGRAM COPYOPENING
CATEGORY = %CATEGORY_SET%
CURRENCY = %CURRENCY_SET%
TID_RA = %TIME%
OTHER = [B_ENTITY=%B_ENTITY_SET%]
*ENDRUN_PROGRAM
*NEXT
Carry-forward business rules
Source account : BALANCE SHEET ACCOUNTS
Source flow : F99
Dest account :
Dest flow : F00
Reverse sign : FALSE
Data source type : ALL
Same period      :FALSE
Apply to YTD : False
Category dimension:
ID               ACTUAL               BUDGET
EVDESCRIPTION          Actual               BUDGET
PARENTH1
YEAR               2008               2011
COMPARISON          BUDGET               NBUDGET
STARTMTH               1               1
CATEGORY_FOR_OPE                    ACTUAL
FX_SOURCE_CATEGORY
RATE_CATEGORY
RATE_YEAR
RATE_PERIOD
FX_DIFFERENCE_ONLY
OPENING_YEAR
OPENING_PERIOD
OWNER               [ADMIN]               [ADMIN]
STORED_CALC
REVIEWER_CAT
Appreciate any help.
Regards
Mehul

Snote 1620613 has fixed the issue
Regards
Mehul

Rejected...We found that your app does not follow the iOS Data Storage Guidelines,

Where and how do I fix this?
We found that your app does not follow the iOS Data Storage Guidelines, which is required per the App Store Review Guidelines.
In particular, we found that on launch and/or content download, your app stores 3.54MB. To check how much data your app is storing:
- Install and launch your app
- Go to Settings > iCloud > Storage & Backup > Manage Storage
- If necessary, tap "Show all apps"
- Check your app's storage
The iOS Data Storage Guidelines indicate that only content that the user creates using your app, e.g., documents, new files, edits, etc., should be backed up by iCloud.
Temporary files used by your app should only be stored in the /tmp directory; please remember to delete the files stored in this location when the user exits the app.
Data that can be recreated but must persist for proper functioning of your app - or because customers expect it to be available for offline use - should be marked with the "do not back up" attribute. For NSURL objects, add the NSURLIsExcludedFromBackupKey attribute to prevent the corresponding file from being backed up. For CFURLRef objects, use the corresponding kCFURLIsExcludedFromBackupKey attribute.

You're submitting a Newsstand app, right? This error is still under investigation, but the current workaround is create SD (1024x768/768x1024) cover images for your HD (2048x1536) folio renditions and try again.
More info here:
http://forums.adobe.com/message/4730637#4730637

JDODataStoreException: The instance null does not exist in the data store

I'm unable to figure out how this exception occurs.
I have a class IDCounter which has a number of fields such as
'm_Name' (String)
'm_AccountName' (String)
'm_UserName' (String)
'm_Description' (String)
'm_CreationDate' (Date)
'm_LastModifiedDate' (Date)
'm_DeletedDate' (Date)
'm_Count' (long)
The filter I'm using is "m_AccountName == \"test\" && m_UserName
==\"test\" && m_DeletedDate == null"
The generated SQL statement is "SELECT t0.M_IDX, t0.JDOCLASSX,
t0.JDOLOCKX, t0.M_ACCOUNTNAMEX, t0.M_CREATIONDATEX, t0.M_DELETEDDATEX,
t0.M_DESCRIPTIONX, t0.M_LASTMODIFIEDDATEX, t0.M_NAMEX, t0.M_USERNAMEX,
t0.M_COUNTX FROM ABSTRACTENTITYX t0 WHERE ((t0.M_DELETEDDATEX IS NULL) AND
t0.JDOCLASSX = 'com.ewarna.pdm.entities.IDCounter')"
Exception Trace:
javax.jdo.JDODataStoreException: The instance null does not exist in the
data store.
     at
com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.instantiateRow(LazyResultList.java:165)
     at
com.solarmetric.kodo.impl.jdbc.runtime.LazyResultList.get(LazyResultList.java:96)
     at java.util.AbstractList$Itr.next(AbstractList.java:416)
     at
com.solarmetric.kodo.runtime.ResultListIterator.next(ResultListIterator.java:49)
     at
com.solarmetric.kodo.impl.jdbc.runtime.ResultListFactory.createResultList(ResultListFactory.java:85)
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.executeQuery(JDBCStoreManager.java:646)
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.executeQuery(JDBCQuery.java:150)
     at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:580)
     at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:428)
     at
com.solarmetric.kodo.query.QueryImpl$SynchronizedQuery.execute(QueryImpl.java:1331)
     at
com.ewarna.pdm.sessions.persistence.BasicQuery.getByAdvancedFormula(BasicQuery.java:78)
     at
com.ewarna.pdm.sessions.persistence.BasicQuery.getByFormula(BasicQuery.java:119)
     at
com.ewarna.pdm.sessions.persistence.BasicQuery.getByFormula(BasicQuery.java:95)
     at
com.ewarna.pdm.sessions.persistence.BasicQuery.getAll(BasicQuery.java:131)
     at
com.ewarna.pdm.sessions.persistence.GenericEntityManager$7.execute(GenericEntityManager.java:305)
     at
com.ewarna.pdm.sessions.persistence.GenericEntityManager.execute(GenericEntityManager.java:251)
     ... 18 more

Youcan no longer display a workbook. You receive an error message when opening: <Internal error>: 1201 document storage
Cause and prerequisites
In very rare cases, when you store a workbook, you might not be able to open it again.
Solution
Function module BDS_PHIOS_GET_RIGHT has to be changed so that the last available version of the Workbooks can be displayed.

When the apple review team review our app,they point out that our app uses a background mode but does not include functionality that requires that mode to run persistently.but in fact,when the app in background ,the app need data update to make the

when the apple review team review our app，they point out that our app uses a background mode but does not include functionality that requires that mode to run persistently。but in fact，when the app in background ，the app need data update to make the function of trajectory replay come ture。in fact， we have added function when the app is in background mode。we have point out the point to them by email。but they still have question on the background mode，we are confused，does anyone can help me，i still don't know why do review team can't find the data update when the app is in background and how do i modify the app，or what is the really problem they refered，do i misunderstand them？
the blow is the content of the review team email：
We found that your app uses a background mode but does not include functionality that requires that mode to run persistently. This behavior is not in compliance with the App Store Review Guidelines.
We noticed your app declares support for location in the UIBackgroundModes key in your Info.plist but does not include features that require persistent location.
It would be appropriate to add features that require persistent use of real-time location updates while the app is in the background or remove the "location" setting from the UIBackgroundModes key. If your application does not require persistent, real-time location updates, we recommend using the significant-change location service or the region monitoring location service.
For more information on these options, please see the "Starting the Significant-Change Location Service" and "Monitoring Shape-Based Regions" sections in the Location Awareness Programming Guide.
If you choose to add features that use the Location Background Mode, please include the following battery use disclaimer in your Application Description:
"Continued use of GPS running in the background can dramatically decrease battery life."
Additionally, at your earliest opportunity, please review the following question/s and provide as detailed information as you can in response. The more information you can provide upfront, the sooner we can complete your review.
We are unable to access the app in use in "http://www.wayding.com/waydingweb/article/12/139". Please provide us a valid demo video to show your app in use.
For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. When the DTS engineer follows up with you, please be ready to provide:
- complete details of your rejection issue(s)
- screenshots
- steps to reproduce the issue(s)
- symbolicated crash logs - if your issue results in a crash log
If you have difficulty reproducing a reported issue, please try testing the workflow as described in <https://developer.apple.com/library/ios/qa/qa1764/>Technical Q&A QA1764: How to reproduce a crash or bug that only App Review or users are seeing.

Unfortunately, these forums here are all user to user; you might try the developer forums or get in touch with the team that you are working with.

Payment Wizard - Series period does not match current period

Hi All,
I've a problem during creation of Incoming Payment through Payment Wizard.
0 payments were added at the end of creation Incoming Payments--> Bill of Exchange using Payment Wizard.
In Non-Included Transactions I can read: series period does not match current period
I've examinated the incaming payment's numbering series and the relate series to document and everything seems ok, so I don't understand the reason of error.
If I try to add the same Incoming payment> Bill of exchange manually in Banking>Incoming Paymenti-->Incoming Payment (without Payment Wizard) it works perfectly!!!
Can you help me?
Simona

Hi Simona,
In step 2 of the Payment Wizard, please check that you have selected the correct series for Incoming Payment at the bottom of the screen.
Hope it helps,
Jesper

Error: web template does not exist in master system

I have Bex 7x query. I wnat to publish it on SAP enterprise portal (EP 7.0 SP19).
When I create a Bex iview and provide link of query, I get following error in preview:
The webtemplate <queryname> does not exist in master system.
Could you please let me know what can be the root cause of this error?
Regards,
Deepti

Dear Deepti,
Can you please make sure that Web template "0ANALYSIS_PATTERN" is acive in your system. If not, please activate it from
Business content.
You can check this by following below steps:
Please run TX SE38 and Execute Report RS_TEMPLATE_MAINTAIN_70 and enter the template name and execute.
If you could see the HTML code , this means it is activated.
Could you also please confirm me the settings you have in TX RSCUSTV27.
Regards,
Arvind

HT4157 I have an iPad 2 and it does not display the cellular data button under settings

I have an iPad 2 and it does not display the cellular data button under settings. It does display a Bluetooth button in its place. I have tried the reset but no luck

Is the iPad the Cellular version? Does it have an active Data plan? Does it have a Sim card installed in inside it?

LOV does not show newly added data in the same session

Hi guys,
I work with JDeveloper 11g Release 2. We use Oracle ADF to develop our web app.
In a page we have a LOV (say the page name is "a"). The related data for that LOV is inserted to the db in another page ( say the page name is "b").
When new data is added in the page "b" and goes directly to the page "a" the LOV does not show newly added data. But if the user log out and log in again
LOV shows newly added data correctly.
Is there a way to show the newly added data in the same session without logging out? Please help.
Regards !
Sameera.

Add the following method in your ViewRowImpl base class:
public void refreshLOVAccessorQueries() {
    List lovs = getViewDef().getListBindingDefs();
     if (lovs != null) {
         for (Object obj : lovs) {
            getListBindingRSI((ListBindingDef)obj).getRowSet().executeQuery();
             ListBindingDef lbd = (ListBindingDef)obj;
Export that method to the Row Client interface, add him to the pageDef, and invoke in the executables section of the pageDef:
    <executables>
<invokeAction Binds="refreshLOVAccessorQueries" id="callRefreshLOVs"
RefreshCondition="#{!requestContext.postback and empty bindings.exceptionList}"/>
   </executables>

Series period does not match current period

Dear Experts...
I got error when update UDF in A/R Invoice form year 2010-11. Year 2010-11 is unlocked and in Document Numbering series it is locked.
Error is Series period does not match current period
How to fix this issue?
Any help will be appreciated.
Regards,
Ravi

Dear Ravi,
First unlock your All A/R document numbring series.
Than go to posting period and unlock you all posting period.
than try and let me know.
Waiting form you reply.
Mangesh Pagdhare.

Payroll period does not correspond to master data error in INLK run & soln

Similar Messages

Maybe you are looking for