Posting rule to be specified in target field of mapping area/Mapping prefix in Search string use?

Posting rule change using search string configuration
Hello Friends - I have defined Search string and specified Posting rule in target field of mapping area and set up done on Search search use tab.
When I imported the Statement, based on text found on statement, Posting rule specified in Search string is determined.
I see Search strings already maintained in my system that Posting rule is maintained in Search string use tab - Mapping prefix.
My doubt is that if Posting rule can be maintained in any of the below:
Either at Posting rule to be specified in target field of mapping area or Mapping prefix in Search string use?
Thanks

Hello Kalim - Thanks. I have already configured Search string the way you suggested me last time and imported the statement during testing. It is working fine.
Can you pls tell me in which scenario "mapping prefix field" should be maintained. Now, I will try to understand this from F1 help.
For Search Strings already defined in our System long ago that Posting rule is not specified in Target field in mapping field, but maintained Mapping prefix.
Thanks,
GT

Similar Messages

Derivation rule CO-PA, number of target fields

Hi all,
is there a possibility to have more than 6 target fields in a CO-PA derivation rule or is the only way to handle more fields with a separate rule based on the same source field?
thanks for your help
kind regards
Adrian

Dear Adrian,
If you want to update more than 6 target field in one derivation step, as for I know is not possible but create a new derivation step with same source and additonal target fields, otherwise use exits.
Regards
Ravi

Product costing error while defining posting rules

Hi Friends,
When I'm trying to define posting rules for settling WIP using OKG8,
I get an error msg "GL account 7000100 cannot be created as a cost element" and the aforesaid account is WIP (P&L account).
The long text of the error msg is as follows:
G/L account 7000100 cannot be created as a cost element
Message no. KQ119
Diagnosis
When maintaining the posting rules for passing on results analysis data to Financial Accounting, you entered a G/L account that is defined as a primary cost element in cost and revenue element accounting. This is not allowed. You must enter a G/L account in the posting rules that is not defined as a cost element.
System Response
The entry invalid.
Procedure
You have the following options:
Enter a G/L account for which no cost element is specified in Cost and Revenue Element Accounting.
You can change the message type with user-defined error management (transaction OPR4_KKA). What should be observed when you enter a G/L account in a posting rule that is defined as a primary cost element in Cost and Revenue Element Accounting? You need to define a CO account assignment so that the posting defined in the posting rule can be executed. You do this with transaction OKB9 (default account assignment) or OKC9 (substitution), or using the default account assignment in the cost element master.
Could anyone suggest me on this.
The steps that I've already defined as far as the account are concerned:
1. Have defined the aforesaid account as a cost element
2. Assigned Prodn. C CTR in OKB9 agnst the same.
But then I dont understand why the system pops up this msg, saying, cannot be created as a cost element, wherein the account is already a cost element.
Plz suggest
regards
sandhya

Hiya,
WIP accounts (neither Inventory nor Offset) should NEVER be created as Cost Elements.
In most manufacturing scenarios, costs are tracked on the P&L. During period-end, since there is the risk of writing off some issues to the Production/Process/Sales Order, SAP has introduced the complex but ingenious system called Results Analysis that moves the balance of all open Orders to the Balance Sheet.
If the Order balance is (+)ve, the P&L is credited and the Balance Sheet is debited and vice versa. When you display the Order costs at period-end, the WIP costs are not considered. In order to calculate WIP, we have separate RA GL accounts that track costs independently of the Orders. Therefore, these are never created as Cost Elements. Creating these as Cost Elements would force the system to inadvertently post the WIP costs back on the Order (alongwith posting these to the B/S??? - an unimaginable situation).
At period-end, you have postings like:
Dr WIP Inventory Account
Cr WIP Offset Account
and, this is reversed at settlement:
Cr WIP Offset Account
Dr WIP Inventory Account
Along with this, the system calculates the Actual COS for the finished product. Neither of the two WIP accounts used above is created as a Cost Element. If you have created any of these as Cost Elements, the system will not allow you to save OKG8. Delete the Cost Element and then try saving the posting rule.
(PS: The "Cost Element" field in this screen has a different use. It is used to specify if a Secondary Cost Element from the RA Update table should be posted to a G/L Account. This is not meant for Primary Cost Elements. I think these Secondary CEs are of type 31 (requires confirmation - no SAP access right now). As you may have guessed, you can only enter either the RA Category or this Secondary CE).
You may also delete the OKB9 assignment to the Cost Centre. It is redundant.
Hope this helps.
Cheers.

Bank Statement Processing - FF_5 - FEBA - Posting Rules

Hi All SAP Experts !!!
I am a non SAP expert (I am a tehcnically minded accountant) trying to find out if I can find a SAP solution to my problem.
I am trying to introduce automatic processing / upload and posting of journals from electronic Bank statements from Citibank.
My particular problem is in the area of processing Cash/Customer receipts which can come from various
different external transaction types from my bank statement.
I have tested a solution whereby the e-bank statement is queried for Invoice numbers with some success but
my problem is the success depends on the accuracy and completeness of Invoice numbers provided by my cusomters.
The above solution when it works makes the following accouNting entries
Level 1 Dr Bank A/c Cr Suspense A/c (General Ledger)
Level 2 Dr Suspense A/c Cr A/R Subledger (Clearing the Customer Invoices)
Due to the lack of consistancy in results of testing I now wish to do something different
Query the same statement on the basis of Customer Name or Customer Bank Details (Bank Orig ID)
From this I would simply like to make the same level 1 posting as above but for the Level 2 posting I simply
want to leave the monies received unallocated on the subledger (ie FBO1 or Not clearing anything)
Is it possible to query the E-Bank statemnent on a name or Bank Originatiing ID and use same to map to a
Customer No within one of SAP's tables ie "Widget & Co" = Cust No 10001 in the AR subledger?
Can the above FB01 Level 2 type transaction be carried out just posting and not allocating/clearing?
Thanks a million
MJOAP40

In the definition of the level 2 posting rule, you have a couple of options. You can leave the posting rule type as a subledger clearing and specify a "Posting on acct key". With that SAP will attempt to clear, but if it can't it will use the posting key specified to post on account (FB01).
Another option is to change the posting rule posting type from clearing the subledger to posting to the subledger - in this case, SAP will not attempt to clear anything, but just post everything on account.
In either scenario, if the system does not have an invoice to clear, then you will probably need to use a search string to assign the customer number so the system knows what account to use for the on account posting. Search strings look at the remittance information on the bank statement (Note to Payee). You would need to create search strings specific to each customer. The search string would map the customer's remittance information to the customer's number in SAP. There are multiple posts in this forum and the ERP Financials - Treasury Applications forum regarding configuration of search strings.
Regards,
Shannon

Posting rule - Cheque Bounce - Bank Statement Processing

Hi friends,
I am configuring for bank statement processing.
Among the posting rules I have to set, I am doubtful about the posting rule (debit, cridit, & account symbol.) for the 'cheque deposited bounced' & 'cheque issued bounced' transaction.
Kindly offer your valid advice on this.
Points will be given for the helpful answers.
Regards
Babu

In the definition of the level 2 posting rule, you have a couple of options. You can leave the posting rule type as a subledger clearing and specify a "Posting on acct key". With that SAP will attempt to clear, but if it can't it will use the posting key specified to post on account (FB01).
Another option is to change the posting rule posting type from clearing the subledger to posting to the subledger - in this case, SAP will not attempt to clear anything, but just post everything on account.
In either scenario, if the system does not have an invoice to clear, then you will probably need to use a search string to assign the customer number so the system knows what account to use for the on account posting. Search strings look at the remittance information on the bank statement (Note to Payee). You would need to create search strings specific to each customer. The search string would map the customer's remittance information to the customer's number in SAP. There are multiple posts in this forum and the ERP Financials - Treasury Applications forum regarding configuration of search strings.
Regards,
Shannon

HOW TO DEFINE POSTING RULE IN BRS STEPS

Very Good Morning SDN Community,
   any budy please let me know what is the logic behind defining the posting rules and how does it works.
The following are the posting rules.
   1. Cheque Deposite
   2. Cheque Issue
   3. Main Bank
   4. Bank Charges.
Now what should be the posting Area, Debit, Credit, posting Key, Account symbol, document type and posting type...
Thanks,
Have a nice day....

Hi,
Please refer to
http://www.sap-topjobs.com/bankreco.pdf
Regards

EBS: Posting on account to Customer through search string

We are attempting an on account posting to the customer account based on the customer name in the bank statement. The configuration looks as follows.
1. Posting rule reflects the setting for posting area 1 and 2. For the second posting area the credit account is blank with posting key 15 and posting type 3
TL04, 1, 40, BANK, 50, BANK TRANSITORY, SA, 1
TL04, 2, 40, BANK TRANSITORY, 15, (BLANK), DZ, 3
2. The search string maps the customer name to customer number
3. The search string use looks as below
BDC Account type = 3
BDC Field name = RF05A-NEWKO
BDC Field Value = Customer number (as mapped to the search string)
4. No interpretation algorithm is used both in search string and in assignment of exterrnal transaction types to posting rules
The second posting to customer cannot be created and it is not able to use the customer number defined n the search string. The value * is passed and goes in error log. Please share your inputs.
Thanks,
Rupesh

Rupesh,
refer to below link which gives more flexibility by using USER EXIT.
http://www.se80.co.uk/sapfms/e/exit/exit_rfebbu10_001.htm
Using exit EXIT_RFEBBU10_001 and structures
FEBEP or FEBKO or FEBCL . You abapper would help you further.
Thanks

COPA derivation rule :more than 6 target fields

Hi ,
As per client's requirement I need to include 10 target fields in a COPA derivation rule . Now after entering 6 , I can see rest of the rows are greyed out ; it looks like SAP does not allow more than 6 as target .
I tried to find out if such limitation is mentioned anywhere in SAP documentation but I could not find ; if anyone has any reference doc on that please let me know .
Secondly , how to meet the requirement ? I can break the same into 2 separate derivation , say 6 target & related rule value in the first and in just next step another 4 targets & rule value ; the source remains same in both the step .
OR any COPA user exit / enhancement will help me accommodate all 10 targets in a single step of derivation ? as far as my knowledge goes SAP provided COPA user exits (1 to 5) will not be helpful here .
Awaiting your help ...
Regards
Indranil Sen

Dear Indranil Sen,
As per my knowledge it is not possible to mention more than 6 source and target fields for a derivation rule.
Because for that program, SAP defines that (1+5) fields for that screen.
That is the reason you are getting the gray color after 6 entries
Yes we can increase that limit but for that we need the access key.
If you have access key authorization, you can increase the limit
Reasons in detail:
Screen filed what you are looking for is:
DYNP5400-SRC-NAME-FIELDNAME
There you can enter (1+5) entries only. enhancement for that field is difficult.
So you can opt for 2nd option as you said.
Let see Mr. Waman Shirwaicar's views on this issue.
Regards,
Pavan Kumar Arvapally

Rule 73 (target field: 0RPA_OID group: 01 Standard Group): Syntax erroer

Hi All,
two formulas (to uppercase) in the transfer rules maping
after the migration of transfer rules,activation of transfermation i am getting this error for two fields.
Rule 73 (target field: 0RPA_OID group: 01 Standard Group): Syntax error in formula.
can anybody tell me how to resolve it.

Hi ,
This is a common problem which we get after migrating to BI7 .
Do one thing copy the formula some where and delete the formula save it activate it . then create the formule once again .
save it and then activate it . You will not get syntax error any more .
Regards
Santosh

Key rule 2 (target field: M1_SUN): Initial update set

HI
friends,
while creating transformations for my character i gave initial
i am getting this message
Key rule 2 (target field: M1_SUN): Initial update set
initial means blank, so my output values should be blank for material, ple let me know.
regards
suneel.

Hi Suneel,
Normally you would want to load data for an InfoObject, so if you are not, the system just warns you. Like you also get warning when adding or removing nav attr from an InfoObject. Even if you are doing that for a reason, the system will prompt with warnings before activating the object.
Hope this helps...

Picking up required Characteristics from my Source field to Target field!!

Hi ,
I need to pick up data from a source field that is 35 characters long to a target field in my Cube that is only 4 char long. But the data that will be fed into this source field will be 4 char long only, so can anyone help me with picking up only the 4 char I need into my target field.
Is this possible, If yes kindly post the routine that will allow me to concatenate the remaining characteristics and pick up only the 4 char I need.
Thanks,
Guru.

Also, if this is the behaviour of the infoObject at all the places it is to be used, you can created Global Transfer Routine at infoObject level.
Otherwise you can write the routine in transformations, rule type "Routine" and then the avaiable source field can be used.
A simple example:
I needed to build a character date field for a cross-platform integration project I was working on. First, I defined the date field:
data: datechar(10).
To build the date lets use sy-datum, which has the current system date.
write SY-DATUM+4(2) to datechar+0(2).
write '/' datechar+2(1).
write SY-DATUM+6(2) to datechar+3(2).
write '/' TO datechar+5(1).
write SY-DATUM+0(4) to datechar+6(4).
Value of SY-DATUM 20010616
Here's how the field changes with the execution of each line.
06________
06/_______
06/16_____
06/16/____
06/16/2001
Hope this helps.
Cheers,
Sumit

Posting rule Standard in FEBAN

Hi,
      What is the field Posting rule Standard in FEBAN selection screen . This is basically the febep-vgdef. I am not sure what it is.
Thanks,
Raja.

Hi,
This field specifies teh rules for posting in the general ledger and subledger.
The above is the explanation if you press F1.
in img while defining the posting rules the following are to be defined.
1)posting rule -
2) Posting area -
        - bank accounting
        - sub ledger
and we have to specify debit / credit posting keys & posting type.
so based on the above posting rules system will decide which account to be debited/credited and which account has to be cleared while posting the FEBAN transaction (normally the clearing account will be either outgoing / incoming payment account)
thanks & regards,
shashi kanth.

Bank statement search string for posting rule 2

Hello,
I created a search string (also activated) for clearing sub legder account. Folowing are the combinations i tried:
1) ###(.| )#######
2) (^| )###(.| )#######( |$)
3) ###.#######
Open document reference text on header normally carries 3digits followed by a dot and then seven digits. For example:
123.1234567. I also want to include 123 1234567 (sometimes it appears like this in bank statement) but the system should intrepret it as 123.1234567.
I think above string acheived this when i did a TEST (button) next mapping screen on the same screen.
I uploaded the bank statement and then went to another config where you do simulation for a bank statement (uploaded). There the system checks for first three digits only and the document found coloumn is blank (because it checks only first three digits and there are too many probable customers in partner's field).
Posting rule - algorithm is no 21
search string - algorithm is no 21
mapping field in search string - i tried with bland and without blank (###.#######) it is all same.
How to make the system check 3+7 digits with dot? and why it checking only first three digits. Can some help?
BG

Hi,
I also would be interested to know this. If anybody can give a step by step analysis, it would be highly appreciated.
Regards,
Ravi

Report for Posting Rule details for Functions/items

Hello
Is there a standard program in SAP to take a report or listing of extract in MS Excel of the posting rule details configuration settings in SAP-JVA. I am fairly certain there is a program to extract the details in Excel but I am not sure what is the name of that program and how to use it. I appreciate any ABAP programmer or expert can guide me how to go about this listing.
Thanks

Hi Raghavendra,
In order to do postings in JVA, we create posting methods and under that Posting method we have to create and configure posting rules. Under the posting method, there are SAP JVA processes or functions and function items that are used to create the posting rules. The posting rules details are specified for each function and function item combination and involve the specification of Recovery indicator along with posting keys, SE indicator and billing indicator.
I am not convinced that the standard codes in my system for posting keys, recovery indicators and billing indicators are exactly the same as the default settings and I need to check it along with the posting rule details.
Please see the screenshots attached to give you an idea. I am looking for an ABAP program or report program to take out a listing of these posting rules details from the system.
Spro - JVA - Posting rules fig 0
Posting method / Posting rules screen - fig 1
Posting rule item codes for function CCOP
Posting rule details for function/item CCOP/AC

Mapping Issue. Parsing problem to target Fields based on condition.

Hi All,
File to Idoc scenario.
My file looks like below.
HD 89650 28/01/11 "Presciber tan"
AF "disc-rsn"
RK "007287001" A
KE disc-code "007287"
KE addr-num "001"
DF fax-num ""
DF in-out "I"
DF phone-2 "23221"
AF "drs"
RK "007287" A
KE dr-num "00221"
KE addr-num "001"
DF affil "OPSM"
DF rec-stat "A"
DF phone-2 "12444"
AF "disc-rsn"
RK "dr-addraddress-1 17287|1EN" A
KE disc-code "008287"
KE field-name "address-1"
KE element " 1"
DF in-out "I"
DF phone-2 "1232"
DF post-code "3109"
DF provider-num "5349201J"
DF rec-stat "A"
T 24
I need to capture and create target segments only for the values "AF "disc-rsn"".And pass all the relavant rows (RK,KE,DF...) which are under "AF "disc-rsn"" to the target fields.
I'm struggling to parse the value to the output structure as RK,KE,DF will be present under anywhere like "AF drs", "AF disc-rsn" etc.
I'm able to create the target segments (2 Zdisc segments as 2 "AF disc-rsn" present in the file), but unable to parse the field values to the target fields.
Ex: DF phone-2 is present in 8th, 15th,22nd row. I need to pass only 8th and 22nd rows to the target fields.
After content conversion, My Source XML looks like below.
<?xml version="1.0" encoding="utf-8" ?>
- <MT_DiscountDetails>
- <HD>
<KeyField>HD</KeyField>
<HDRow>89650 28/01/11 "Presciber tan"</HDRow>
</HD>
- <AF>
<KeyField>AF</KeyField>
<AFRow>"disc-rsn"</AFRow>
</AF>
- <RK>
<KeyField>RK</KeyField>
<RKRow>"007287001" A</RKRow>
</RK>
- <KE>
<KeyField>KE</KeyField>
<KERow>disc-code "007287"</KERow>
</KE>
- <KE>
<KeyField>KE</KeyField>
<KERow>addr-num "001"</KERow>
</KE>
- <DF>
<KeyField>DF</KeyField>
<DFRow>fax-num ""</DFRow>
</DF>
- <DF>
<KeyField>DF</KeyField>
<DFRow>in-out "I"</DFRow>
</DF>
- <DF>
Is there any way I can acheive my mapping based on the above condition?? Kindly suggest me.
Thank you for your time.
Regards
Deepthi

Not required. Using Java function. Solved the issue.

Posting rule to be specified in target field of mapping area/Mapping prefix in Search string use?

Similar Messages

Maybe you are looking for