Sign-in rule

In Business catalyst, when creating a sign in page:
Is there a way to set a sign-in rule for example: all emails must end in @sci-us.com

Hey there,
You would need to code that with javascript. Some use of regular expresion or indexOf would be needed.
You able to do that or need help?

Similar Messages

Creating Logic for FDM Sign Flip Rule

I am working through an implantation of FDM (11.1.2.2) for a Hyperion Enterprise environment and we have > 70 different locations to create. Some will share a common parent, but most will not. We were using HAL prior to FDM and HAL would allow us to utilize a Sign Flip Rule for the load to Enterprise, but FDM, as you're aware, works in a considerably different manner.
For HAL we had a list of high-level accounts that we knew would need to have their sign flipped before loading to Hyperion, and we could use a wildcard to work for this account. For example, when "Accounts" = "CashEquiv*" then "0". Using this method, we were not required to specifically required to identify each individual sub account, rather we could just call out out the first-level account and say that anything that falls below that, should be flipped. Is there any way to do this in FDM? Would it possible to write logic to do this? Individually selecting each tick box for each account is going to take forever.

There is no out of the box functionality to replicate what you want to do. I suggest you export the account mappings from FDM into excel, manage the sign flip there and re-import to FDM. This will be much faster than doing it via the web interface

Which way is better to reverse a key figure sign, update rule or KF prop.?

We are trying to reverse a key figure sign and have got two options:
1. In Update Rule by using formula to make this key figure * 1-, or
2. In key figure property of query design mode, there is a checkbox of "Reverse +/- Signs".
Which one is better for the above two options?
Thanks
Message was edited by: Kevin Smith

Hi,
1. In Update Rule by using formula to make this key figure * 1-, or
A: If you want to update data permanently in Data Targets then go for update rules.
2. In key figure property of query design mode, there is a checkbox of "Reverse +/- Signs".
A: The data is not updated in Data Targets but while displaying in Reports it will display the sign.
That is upto you and business requirements.
Thanks
REddy

Plus sign normalization rule

Hi all,
I am new to Lync so pardon in advance.
I have a set of normalization rules that allow a user to dial a number starting with a plus sign. this works fine for me (North America) while dialing international numbers. what I have today removes the + , adds +011. But more often than not there
are north american numbers that have plus sign. this would translate a +17162223333 to +0111716222333 which is not correct.
Can someone help me as to how create a rule that would leave out north american numbers?
cheers

I agree with Michael, Ken Lasko is the kind of Lync dial plans, definitely read that article, it should clear a lot up. Ken also has tools for automatically creating Dial Plans with proper normalization.
The + is the 011, they're the same prefix, just in different formats. You should never have +011 as a result, even on international numbers, because it's redundant.
So, a US phone number dialed as 17162223333 should normalize to +17162223333 and a South African phone number dialed as 01127315551212 should normalize to +27315551212. As it leaves Lync, you may need to modify that so your Telco
understands it, so at the gateway you might strip the +, or +1, and you may need to add the 011 at your gateway or as a translation rule on your trunk.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Use of "&" in rules

Hi Gurus,
I am new to rules, i have to understand some code and need to modify. I very new to rules. I have a doubts regarding rules. What is the use of "&" sign in rules? How do we use this in rules? And could you plz explain below statements.
1) HS.Exp “A#BegRetainedEarnings ”&“= A#EndRetEarn.Y#Prior.P#Last ”&“+ A#NetIncome.Y#Prior.P#Last.W#YTD” -- in this statement what is the use of "&" and how it works.
2) HS.Exp "A#Account3.C1#Computers = " & SomeVariable --- In this stament "&" use and how it works.
3) HS.Exp “A#Account3.C1#Computers = A#Account4 “ & “.C1#Computers * 1.1” -- Plz explain this statement and *".C1#Computers"* . with out specifying other dimensions, what is the purpose of ".C1#Computers".
Thanks and regards
nivas

Ampersands is your concatenation symbol, it is used to add a variable to a text string.
HS.Exp “A#BegRetainedEarnings ”&“= A#EndRetEarn.Y#Prior.P#Last ”&“+ A#NetIncome.Y#Prior.P#Last.W#YTD”
The ampersand appears to be unnecessary in the above example this should work
HS.Exp “A#BegRetainedEarnings = A#EndRetEarn.Y#Prior.P#Last+ A#NetIncome.Y#Prior.P#Last.W#YTD”
You can test this by scanning your rules.
HS.Exp "A#Account3.C1#Computers = " & SomeVariable --- In this stament "&" use and how it works.
if your variable equals Banana, the equivalent string would be HS.Exp "A#Account3.C1#Computers = Banana" meaning whatever the value of the variable is what it will be appended to the string.
HS.Exp “A#Account3.C1#Computers = A#Account4 “ & “.C1#Computers * 1.1” -- Plz explain this statement and ".C1#Computers" . with out specifying other dimensions, what is the purpose of ".C1#Computers".
Again the ampersand appears to be unnecessary.
The purpose of ".C1#Computers", is to limit the value placed on your target account to that of the Computers Member of the Custom 1 dimension.
Please take the following statement the right way: Before venturing into the rules file, learn some VBA.
Edited by: Raul Rodriguez on Feb 12, 2011 3:35 PM

FRM-40207 supressed after Business Rule violation

Situation:
- Form based on table with column A number(1)
- Item width in form = 2 (automatic, to enable negative sign)
- Business rule on column: value must be > 0
- Try saving record with column A = -2: Business Rule is violated --> error message (as expected)
- Changing value to 22, no error, not possible to leave record/item: 'FRM-40207 Must be in range -9 to 9' is not shown
- Trying to type 22 first time leads to the 'FRM-40207: Must be in range -9 to 9' message as expected
- Generating the form with teh preference set QMS_DEBUG_MODULE: FRM message is also shown after violation of BR (negative value) (thus it is a Headstart problem?)
- Setting a format mask of 9 on the field does not solve the problem, in that case 'FRM-40209 Must be of format 9' is supressed
It looks like the rule frame/headstart code suppresses the FRM message after violation of a Business Rule,
anybody experienced the same problem or knows a solution?
tia
Geert

I think we came across the same problem as you are describing. We created a temporary workaround for our problem by creating a custom library object using both the <maximum length> and <format mask> properties. This may not be feasible if you have are having the problem with several columns of varying lengths.
[email protected]

XCode target not displaying Code Signing Provisioning Profile

Hello experts,
I am first time uploading my application on the apple store. I downloaded distribution provisioning profile and placed that into home/library/Mobile Device/Provisioning Profiles.
Opened xcode, created distributed configuration by duplicating release configuration.
changed CODE SIGNING IDENTITY to IPhone Distribution: My company name
next step is to set the CODE SIGNING PROVISIONING PROFILE but xcode not showing this option.
The four options that i can see are:
1) Code signing Entitlements
2) Code signing identity
3) Code signing resource rules path
4) Other code signing flags
NOT the "CODE SIGNING PROVISIONING PROFILE" parameter to set.
What i need to check for this.
I tried to upload my app without this setting but as i expected got the error:
"The binary you uploaded is not valid or it was not signed by Apple Submission Certificate."
Please help me to resolve this.
Thanks in advance.

thanks for replying
i checked all the above mentioned steps.
-> My Distibution Profile is present in Mobile Devices/Provisioning Profiles.
-> Active SDK is Device
-> Active Configuration is Distribution
-> Bundle Identifier name is a simple five letter word without white spaces and special characters.
The only thing my application is not having is the "Code Signing Provisioning Profile" option to set in the top-level getinfo window->build.
here i am giving the link of my build settings for Distribution Configuration:
http://reportingmanager.com/NevaGarments/ScreenShot/Picture.png
please let me know what needs to be done.
Thanks

Clearing customer open items

Hello!
Can anybody help to find a way how to clear customer open items when there is no reference number in use for customer. In electronic bank statemen there is only billing document number in TXT field. How to configure "Make Global Settings for Electronic Bank Statement" and "Define Search String for Electronic Bank Statement" for that purpose.
With all the best,
Merlin

Hello,
IMG => Financial Accounting => Bank Accounting => Business Transactions => Payment Transactions => Electronic Bank Statement => Make Global Settings for Electronic Bank Statement
Give your chart of Accounts
1. Create your account symbols
Create freely definable account symbols. Make sure that you are able to identify them when you are configuring in future steps.
2. Assigning Accounts to Account Symbols
Here you need to assign the account symbols to GL Accounts or you need to use masking logic. You must have designed your accounts in such a way that the end digits will work for posting the entries to FI. Account Modifier you use as + and use your local currency, if you do not have any foreign currency postings.
3. Create Posting Rules
Create freely definable posting rules.
4. Define Posting Rules (This is the most important configuration for your FI Postings / Clearings)
a) For all the payments you need to create the entries for posting area 1
b) For all the receipt you need to create the entries for posting area 1 and 2
c) Use the document type DZ in case if you want to clear the items. Use Posting type 8. If the invoice number is there in the reference field of bank statement, automatically the same will be selected by the system and cleared.
d) If you want just only entries to be posted use posting type 1.
e) If you want to clear the check, then use the posting type 4.
f) Configure according to the entries to be posted.
g) If you are going for clearing something the offsetting debit / offsetting credit (as the case may be) need not be given.
5. Create Transaction Type
Create freely definable Transaction Type
Select the transaction type and assign the external transactions to your posting rules.
For outgoing check use 13 as Interpretation Algorithm and 1 as the processing type.
Remaining all case use 1 (Standard algorithm) and 5 as the processing type.
Please also go through the below mentioned note in case if you are required to use further available interpretation algorithms or processing types.
6. Assign Bank Accounts to Transaction Types:
You need enter the Bank Key / Bank Account / Transaction type here.
You can get the the bank key and bank account details from table T012K (Go to SE16)
Further supplementary notes may be useful to you:
There are different programs to upload electronic bank statement.
FF.5 or FF_5.
I think your case Multicash format you are using.
You need have three files in FF.5 and two files in FF_5
You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server.
1. Take all the external codes list from bank.
2. Take any available documentation from the Bank describing the relevance of the external codes.
3. Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements.
4. Based on this decide the Account Symbols that are required to be created.
5. Make sure that the masking rules are configured properly.
6. Decide the posting rules that needs to be created.
7. Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic.
6. Concentrate on the posting areas to be posted while uploading the bank statement.
Further explanation would help you to understand the functionality when uploaded the electronic bank statement.
Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync.
You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP.
SAP is normally you maintain bank main account and bank sub account. Whenever you make a payment through F-53 or F-58 or F110, the entry would be:
Vendor Account Dr
To Bank Sub Account
The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass is:
Bank Sub Account Dr
To Bank Main Account
It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts.
At the time of receipts, you have different accounting entries unlike payments. It needs to post to two posting areas. 1. GL Accounting 2. Sub-Ledger Accounting
The entries would system itself pass is:
Bank Main Account Dr
To Bank Sub Account
Bank Sub Account Dr
To Cutomer account.
Clearing logic mentioned for your posting rules and the alogrithm used for your external bank symbols will also play pivotal role in clearing the accounts.
Ideally you will use
FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement
FEBA / FEBA_BANK_STATEMENT is used for furthe rprocessing.
GO THROUGH SAP NOTE 48854
Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms.
Though this note is in relevant to GB specific, you will find this very useful.
description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point.
The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case.
1. '00': There is no processing. The entry line is ignored.
2. '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm.
3. '02': Transfer of the ending balance to the electronic bank statement
4. '03': Transfer of the opening balance to the electronic bank statement
5. '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm.
6. '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'.
Note
To differentiate between the two procedures in table T028G, you have to maintain two separate entries.
Example: the bank uses bank code '62' for cash receipts and for BACS bank collection.
Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5
62 SAPBACS + GB63 000 5
7. '06': Bank costs or interest revenues
Recommended interpretation algorithm: '000 - No interpretation'
8. '07': Total amount of cash disbursements
9. '08': Total amount of cash receipts
10. '09': Items not paid
Recommended interpretation algorithm: '000 - No interpretation'
Regards,
Ravi

Report for Un-Reconcile items

Hi All,
Hope you all must be doing great,I have one problem related with FI.
we are implementing Manual bank Reconciliation statement at our client place. I am facing a practical problem here. The problem is ;
There are some line items those are present in Bank statement( bank charges, LC payment) but the same financial entry is not there in the SAP system(sap ledger). The user feeds all the data that is in the bank statement and run the BRS. The system is taking the matched data and for un-matched data system is throwing Errors while running the BRS . All thematched & Un matched data stored in a Table FEBEP.
The system is not maintaining any status for those line items which are present in the bank statement but not present in the SAP
I have to develop a report in co-ordination with ABAP for those line items which are present in bank statement but not present in the SAP i.e. for Un-Reconcile items
Kindly look into this case please let me know How this situation is to be handeled?
If possible please let me know the Table & fields involved.
With Regards
Manoj Singh

Hello,
It all depends on how you have configured. If you want to clear the items, the system looks for the algorithm you have given. If you want to make postings then the system itself will pass the entries for the unmatched entries. (Bank Charges, LC Payments). You need not bothered about this. The system credits your main account and debits the sub account. Manually you can pass the contra entry if you do not configure for example credit bank sub account and debit bank charges account (in case if you do not configure).
Please let me know if you need any further help.
Regards,
Ravi
==============================================================
The following notes may useful to you. Please search some of my notes on Bank Statements in other threads.
There are different programs to upload electronic bank statement.
FF.5 or FF_5.
I think your case Multicash format you are using.
You need have three files in FF.5 and two files in FF_5
You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server.
1. Take all the external codes list from bank.
2. Take any available documentation from the Bank describing the relevance of the external codes.
3. Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements.
4. Based on this decide the Account Symbols that are required to be created.
5. Make sure that the masking rules are configured properly.
6. Decide the posting rules that needs to be created.
7. Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic.
6. Concentrate on the posting areas to be posted while uploading the bank statement.
Further explanation would help you to understand the functionality when uploaded the electronic bank statement.
Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync.
You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP.
SAP is normally you maintain bank main account and bank sub account. Whenever you make a payment through F-53 or F-58 or F110, the entry would be:
Vendor Account Dr
To Bank Sub Account
The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass is:
Bank Sub Account Dr
To Bank Main Account
It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts.
At the time of receipts, you have different accounting entries unlike payments. It needs to post to two posting areas. 1. GL Accounting 2. Sub-Ledger Accounting
The entries would system itself pass is:
Bank Main Account Dr
To Bank Sub Account
Bank Sub Account Dr
To Cutomer account.
Clearing logic mentioned for your posting rules and the alogrithm used for your external bank symbols will also play pivotal role in clearing the accounts.
Ideally you will use
FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement
FEBA / FEBA_BANK_STATEMENT is used for furthe rprocessing.
GO THROUGH SAP NOTE 48854
Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms.
Though this note is in relevant to GB specific, you will find this very useful.
description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point.
The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case.
1. '00': There is no processing. The entry line is ignored.
2. '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm.
3. '02': Transfer of the ending balance to the electronic bank statement
4. '03': Transfer of the opening balance to the electronic bank statement
5. '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm.
6. '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'.
Note
To differentiate between the two procedures in table T028G, you have to maintain two separate entries.
Example: the bank uses bank code '62' for cash receipts and for BACS bank collection.
Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5
62 SAPBACS + GB63 000 5
7. '06': Bank costs or interest revenues
Recommended interpretation algorithm: '000 - No interpretation'
8. '07': Total amount of cash disbursements
9. '08': Total amount of cash receipts
10. '09': Items not paid
Recommended interpretation algorithm: '000 - No interpretation'
Regards,
Ravi

EBS statement Assign to Automatic payment programme?

Hello,
The requirment of customer when i run automatic payment progrmme customer want electronic bank statement. in statement detail information bank account of company. how to assign electronic bank statement to automatic payment programme.if any configuration please give me detail .
Regards.
Shailesh.

Hello,
Both are different. Automatic Payment program is outgoing and electronic bank statement is incoming.
There is no direct linkage. For electronic bank statement, you are not the initiator. Your bank is the initiator. Unless, you have the inputs from Bank, you cannot upload the electronic bank statement.
Anyway, the following information may be useful for your electronic bank statement configuration.
Hello,
There are different programs to upload electronic bank statement.
FF.5 or FF_5.
I think your case Multicash format you are using.
You need have three files in FF.5 and two files in FF_5
You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server.
1. Take all the external codes list from bank.
2. Take any available documentation from the Bank describing the relevance of the external codes.
3. Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements.
4. Based on this decide the Account Symbols that are required to be created.
5. Make sure that the masking rules are configured properly.
6. Decide the posting rules that needs to be created.
7. Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic.
6. Concentrate on the posting areas to be posted while uploading the bank statement.
Further explanation would help you to understand the functionality when uploaded the electronic bank statement.
Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync.
You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP.
SAP is normally you maintain bank main account and bank sub account. Whenever you make a payment through F-53 or F-58 or F110, the entry would be:
Vendor Account Dr
To Bank Sub Account
The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass is:
Bank Sub Account Dr
To Bank Main Account
It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts.
At the time of receipts, you have different accounting entries unlike payments. It needs to post to two posting areas. 1. GL Accounting 2. Sub-Ledger Accounting
The entries would system itself pass is:
Bank Main Account Dr
To Bank Sub Account
Bank Sub Account Dr
To Cutomer account.
Clearing logic mentioned for your posting rules and the alogrithm used for your external bank symbols will also play pivotal role in clearing the accounts.
Ideally you will use
FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement
FEBA / FEBA_BANK_STATEMENT is used for furthe rprocessing.
GO THROUGH SAP NOTE 48854
Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms.
Though this note is in relevant to GB specific, you will find this very useful.
description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point.
The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case.
1. '00': There is no processing. The entry line is ignored.
2. '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm.
3. '02': Transfer of the ending balance to the electronic bank statement
4. '03': Transfer of the opening balance to the electronic bank statement
5. '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm.
6. '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'.
Note
To differentiate between the two procedures in table T028G, you have to maintain two separate entries.
Example: the bank uses bank code '62' for cash receipts and for BACS bank collection.
Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5
62 SAPBACS + GB63 000 5
7. '06': Bank costs or interest revenues
Recommended interpretation algorithm: '000 - No interpretation'
8. '07': Total amount of cash disbursements
9. '08': Total amount of cash receipts
10. '09': Items not paid
Recommended interpretation algorithm: '000 - No interpretation'
Regards,
Ravi

TR-EBS SwiftMT940 mapping to an IDOC message FINSTA01 - Bank Statements

For Treasury, we are going to move to the PI platform. We are currently using EDI.
We start the process by requesting Citibank(GXS operations team) to put a sample file into the outbound mailbox to let our company pick up. The output of the file will be XML.
We will them map and create an IDOC with the FINSTA message.
However, we are only beginning the IDOC mapping process.
Does anyone have a sample crosswalk which will allow us to see how the SwiftMT940 from Citibank can be mapped to an SAP Idoc?
If so, may we see how you mapped the segments?
Also, how do you test the loading of the IDOC created? with the RFEBKA00 program?
Please advise.

Hello,
I am really not sure how you map to IDOC.
But, the following information may be useful to you.
Hello, You can configure the electronic bank statement at the following path: IMG => Financial Accounting => Bank Accounting => Business Transactions => Payment Transactions => Electronic Bank Statement => Make Global Settings for Electronic Bank Statement. All the settings will be done at this path only. 1. Create Account Symbols 2. Assign Accounts to Account Symbols 3. Create keys for posting rules 4. Define posting rules 5. Create transaction type Assign external transaction types to posting rules 6. Assign bank accounts to transaction types. There are different programs to upload electronic bank statement. FF.5 or FF_5. I think your case Multicash format you are using. You need have three files in FF.5 and two files in FF_5 You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server. 1. Take all the external codes list from bank. 2. Take any available documentation from the Bank describing the relevance of the external codes. 3. Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements. 4. Based on this decide the Account Symbols that are required to be created. 5. Make sure that the masking rules are configured properly. 6. Decide the posting rules that needs to be created. 7. Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic. 6. Concentrate on the posting areas to be posted while uploading the bank statement. Further explanation would help you to understand the functionality when uploaded the electronic bank statement. Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync. You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP. SAP is normally you maintain bank main account and bank sub account. Whenever you make a payment through F-53 or F-58 or F110, the entry would be: Vendor Account Dr To Bank Sub Account The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass is: Bank Sub Account Dr To Bank Main Account It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts. At the time of receipts, you have different accounting entries unlike payments. It needs to post to two posting areas. 1. GL Accounting 2. Sub-Ledger Accounting The entries would system itself pass is: Bank Main Account Dr To Bank Sub Account Bank Sub Account Dr To Cutomer account. Clearing logic mentioned for your posting rules and the alogrithm used for your external bank symbols will also play pivotal role in clearing the accounts. Ideally you will use FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement FEBA / FEBA_BANK_STATEMENT is used for furthe rprocessing. GO THROUGH SAP NOTE 48854 Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms. Though this note is in relevant to GB specific, you will find this very useful. description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point. The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case. 1. '00': There is no processing. The entry line is ignored. 2. '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm. 3. '02': Transfer of the ending balance to the electronic bank statement 4. '03': Transfer of the opening balance to the electronic bank statement 5. '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm. 6. '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'. Note To differentiate between the two procedures in table T028G, you have to maintain two separate entries. Example: the bank uses bank code '62' for cash receipts and for BACS bank collection. Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5 62 SAPBACS + GB63 000 5 7. '06': Bank costs or interest revenues Recommended interpretation algorithm: '000 - No interpretation' 8. '07': Total amount of cash disbursements 9. '08': Total amount of cash receipts 10. '09': Items not paid Recommended interpretation algorithm: '000 - No interpretation' Regards, Ravi

Bank Manual Statement - FF.5

Hi CFM experts,
while doing FF.5, I am getting error, INR:STATEMENT 200900106 is not in the bank data storage.
actually BDC, session is not created. Kindly provide some solution.
Regards
J. Stephen Thangiah

When you upload the first statement you will get this warning message. Just ignore this.
Hello, There are different programs to upload electronic bank statement. FF.5 or FF_5. I think your case Multicash format you are using. You need have three files in FF.5 and two files in FF_5 You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server. 1. Take all the external codes list from bank. 2. Take any available documentation from the Bank describing the relevance of the external codes. 3. Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements. 4. Based on this decide the Account Symbols that are required to be created. 5. Make sure that the masking rules are configured properly. 6. Decide the posting rules that needs to be created. 7. Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic. 6. Concentrate on the posting areas to be posted while uploading the bank statement. Further explanation would help you to understand the functionality when uploaded the electronic bank statement. Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync. You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP. SAP is normally you maintain bank main account and bank sub account. Whenever you make a payment through F-53 or F-58 or F110, the entry would be: Vendor Account Dr To Bank Sub Account The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass is: Bank Sub Account Dr To Bank Main Account It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts. At the time of receipts, you have different accounting entries unlike payments. It needs to post to two posting areas. 1. GL Accounting 2. Sub-Ledger Accounting The entries would system itself pass is: Bank Main Account Dr To Bank Sub Account Bank Sub Account Dr To Cutomer account. Clearing logic mentioned for your posting rules and the alogrithm used for your external bank symbols will also play pivotal role in clearing the accounts. Ideally you will use FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement FEBA / FEBA_BANK_STATEMENT is used for furthe rprocessing. GO THROUGH SAP NOTE 48854 Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms. Though this note is in relevant to GB specific, you will find this very useful. description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point. The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case. 1. '00': There is no processing. The entry line is ignored. 2. '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm. 3. '02': Transfer of the ending balance to the electronic bank statement 4. '03': Transfer of the opening balance to the electronic bank statement 5. '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm. 6. '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'. Note To differentiate between the two procedures in table T028G, you have to maintain two separate entries. Example: the bank uses bank code '62' for cash receipts and for BACS bank collection. Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5 62 SAPBACS + GB63 000 5 7. '06': Bank costs or interest revenues Recommended interpretation algorithm: '000 - No interpretation' 8. '07': Total amount of cash disbursements 9. '08': Total amount of cash receipts 10. '09': Items not paid Recommended interpretation algorithm: '000 - No interpretation' Regards, Ravi

OATM APPLSYS,FND_CP_GSM_OPP_AQ$4452 related query

I have successfully completed an OATM reorganisation of an Oracle Financials 11-5-10-2 database ...
My only questions is that I have lost two objects, these are :-
A ruleset -> APPLSYS.FND_CP_GSM_OPP_AQ$4452 ,RULE SET,VALID
A rule -> APPLSYS,FND_CP_GSM_OPP_AQ$4452,RULE,VALID
I don't really know what these represent or if this is a problem.
Running query against post oatm dnba_objects gives :-
select owner, object_name, object_type,status
from dba_objects a
where object_name like '%FND_CP_GSM_OPP_AQ%'
and object_type in ('RULE SET','RULE')
OWNER,OBJECT_NAME,OBJECT_TYPE,STATUS
APPLSYS,FND_CP_GSM_OPP_AQ_R,RULE SET,VALID
APPLSYS,FND_CP_GSM_OPP_AQ_N,RULE SET,VALID
Running query against pre oatm dba_objects gives :-
select owner, object_name, object_type,status
from dba_objects_preorg a
where object_name like '%FND_CP_GSM_OPP_AQ%'
and object_type in ('RULE SET','RULE')
OWNER,OBJECT_NAME,OBJECT_TYPE,STATUS
OWNER,OBJECT_NAME,OBJECT_TYPE,STATUS
APPLSYS,FND_CP_GSM_OPP_AQ$4452,RULE SET,VALID
APPLSYS,FND_CP_GSM_OPP_AQ$4452,RULE,VALID
APPLSYS,FND_CP_GSM_OPP_AQ_R,RULE SET,VALID
APPLSYS,FND_CP_GSM_OPP_AQ_N,RULE SET,VALID
As you can see :-
APPLSYS,FND_CP_GSM_OPP_AQ$4452,RULE SET,VALID
APPLSYS,FND_CP_GSM_OPP_AQ$4452,RULE,VALID
APPLSYS,FND_CP_GSM_OPP_AQ<dollar sign>4452,RULE SET,VALID
APPLSYS,FND_CP_GSM_OPP_AQ<dollar sign>4452,RULE,VALID
have disappeared - this could be expected behaviour howevere it would be great tio get an explanation and hopefully a confirmation that this is fine and not a worry.
cheers then, Rob

Hit guys,
Thanks for your inputs ...
I ran the script however as you can see from below no rulesets matching FND_CP_GSM_OPP_AQ$ were
found in the current post oatm system despite running the suggested script (afopp002.sql) :-
select owner, object_name,object_type
from dba_objects_preorg a
where object_name like '%FND_CP_GSM_OPP_AQ$%'
OWNER,OBJECT_NAME,OBJECT_TYPE
APPLSYS,FND_CP_GSM_OPP_AQ$4452,RULE SET
APPLSYS,FND_CP_GSM_OPP_AQ$4452,RULE
So these did exist pre oatm but are gone now - maybe they are obsolete ???
select owner, object_name,object_type
from dba_objects a
where object_name like '%FND_CP_GSM_OPP_AQ$%'
No rows returned
select object_name,object_type,status
from dba_objects_preorg
where OBJECT_NAME like 'FND_CP_GSM_OPP%'
OBJECT_NAME,OBJECT_TYPE,STATUS
FND_CP_GSM_OPP_AQ_PAYLOAD,TYPE,VALID
FND_CP_GSM_OPP_AQ$4452,RULE SET,VALID
FND_CP_GSM_OPP_AQ$4452,RULE,VALID
FND_CP_GSM_OPP_AQTBL,TABLE,VALID
FND_CP_GSM_OPP_AQ,QUEUE,VALID
FND_CP_GSM_OPP_AQ_R,RULE SET,VALID
FND_CP_GSM_OPP_AQ_N,RULE SET,VALID
7 rows ....
After OATM :-
select object_name,object_type,status
from dba_objects
where OBJECT_NAME like 'FND_CP_GSM_OPP%'
OBJECT_NAME,OBJECT_TYPE,STATUS
FND_CP_GSM_OPP_AQ_PAYLOAD,TYPE,VALID
FND_CP_GSM_OPP_AQTBL,TABLE,VALID
FND_CP_GSM_OPP_AQ_N,RULE SET,VALID
FND_CP_GSM_OPP_AQ_R,RULE SET,VALID
FND_CP_GSM_OPP_AQ,QUEUE,VALID
5 rows ...
FND_CP_GSM_OPP_AQ$4452,RULE SET,VALID and FND_CP_GSM_OPP_AQ$4452,RULE,VALID no longer exist the question is, is this expected behaviour or do we need to recreate these somehow ?
Cheers, Rob
Cheers, Rob
Edited by: Diesel on Apr 12, 2011 11:17 AM

Ad Hoc 0xe8000001 error

I am building my App for Ad Hoc Distribution but I am getting a 0xe8000001 unknown error when I try to install it.
It works perfectly in device debug mode, and I have followed all the instructions exactly over and over, but I still get the error.
It doesn't look like there are any problems in the build log either.
I have read in other places a similar problem, but none of their solutions worked for me.
Also, what happened to the forum search?

Sorry Jason I don't have an answer as I am in the same boat, and figured it was better to join you here instead of starting a new thread on my own.
Btw I'm trying to make it work for development mode.
I went through those certificate steps:
1) Generated my certificate and downloaded/installed it in my Keychain
2) Registered my iPhone device
3) Created an AppID in the ##########.* form
4) Created a Provision profile, using my ##########.* id
Then I downloaded the Provision profile, dragged it on my XCode icon, which installed it in its proper folder (home/library/mobile device/provisioning profiles).
In my Organizer window in XCode, I checked the Provision profile on my iPhone device.
Then in my project settings I changed those entries:
[Code Signing Entitlements]: (blank)
[Code Signing Identity]: *
[Code Signing Provisionning Profile]: Default provisionning profile for ...
[Any iPhone OS Device]: Default provisionning profile for ...
[Code Signing Resource Rules Path]: iphoneos2.0/ResourceRules.plist
[Other Code Signing Flags]: (blank)
But when I build, it seems to go through all the process (signing, copying), but I get the dreadful E8000001 error message at the end.
Am I missing a setting? A step?
Thanks for all help!

Electronic bank mt940 step by step configuration document

hi all,
can any body send me a step by step electronic bank mt940 configuration document.
Its little bit important we are implementing mt940 format.
regards,
sudhakar

Hello, Hope the following information is helpful. There are different programs to upload electronic bank statement. FF.5 or FF_5. I think your case Multicash format you are using. You need have three files in FF.5 and two files in FF_5 You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server. 1. Take all the external codes list from bank. 2. Take any available documentation from the Bank describing the relevance of the external codes. 3. Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements. 4. Based on this decide the Account Symbols that are required to be created. 5. Make sure that the masking rules are configured properly. 6. Decide the posting rules that needs to be created. 7. Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic. 6. Concentrate on the posting areas to be posted while uploading the bank statement. Further explanation would help you to understand the functionality when uploaded the electronic bank statement. Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync. You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP. SAP is normally you maintain bank main account and bank sub account. Whenever you make a payment through F-53 or F-58 or F110, the entry would be: Vendor Account Dr To Bank Sub Account The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass is: Bank Sub Account Dr To Bank Main Account It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts. At the time of receipts, you have different accounting entries unlike payments. It needs to post to two posting areas. 1. GL Accounting 2. Sub-Ledger Accounting The entries would system itself pass is: Bank Main Account Dr To Bank Sub Account Bank Sub Account Dr To Cutomer account. Clearing logic mentioned for your posting rules and the alogrithm used for your external bank symbols will also play pivotal role in clearing the accounts. Ideally you will use FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement FEBA / FEBA_BANK_STATEMENT is used for furthe rprocessing. GO THROUGH SAP NOTE 48854 Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms. Though this note is in relevant to GB specific, you will find this very useful. description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point. The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case. 1. '00': There is no processing. The entry line is ignored. 2. '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm. 3. '02': Transfer of the ending balance to the electronic bank statement 4. '03': Transfer of the opening balance to the electronic bank statement 5. '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm. 6. '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'. Note To differentiate between the two procedures in table T028G, you have to maintain two separate entries. Example: the bank uses bank code '62' for cash receipts and for BACS bank collection. Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5 62 SAPBACS + GB63 000 5 7. '06': Bank costs or interest revenues Recommended interpretation algorithm: '000 - No interpretation' 8. '07': Total amount of cash disbursements 9. '08': Total amount of cash receipts 10. '09': Items not paid Recommended interpretation algorithm: '000 - No interpretation' Regards, Ravi

Sign-in rule

Similar Messages

Maybe you are looking for