Logic for Automatice AccountID generation for B2C Accounts

I have noticed that the accountIDs for B2C accounts are of the form WEB245df2f283ce.
The WEB prefix is a configuration setting.
What is the algorithm or class used to generate this random(?) string. I noticed there is a method CREATE in the class NPAccount but I hoping to use SQL to bulk sync the users/usersAccount table with an external membership database.
Perhaps ... if the only requirement is that the ACCOUNTID's be unique then perhaps I can create my own as long as they don't conflict with any already existing? Would that work if created my own random suffix to the WEB-accountid?

I'm not sure what class is used but in the Setup / Config Settings / Netpoint dropdown there is a checkbox for auto generating account id's. You could try unchecking this and see what happens .. I think it tries to create the account based on the userid.
If you want to create your own accounts in code, you're right they just need to be unique so you can use whatever logic you want.

Similar Messages

GR/IR Rounding Logic for Multiple Account Assignment

We have activated business function LOG_MM_MAA_1 (EHP4 release 604), GR valuated. When choosing Distribution on quantity basis and distribute partial inv proportionally, the MIGO postings are different from the MIRO postings. For example, we have a quantity of 12 that we allocate to two different cost centers 33.3 / 66.7 %. We receive a partial qty of 5. MIGO distributes the quantity 1.665 / 3.335, respectively. However, MIRO distributes the quantity 1.666 / 3.333 respectively. Since MIRO is supposed to accept the MIGO quantities and amounts, why is the percentage allocation different? Is there a way to make the percentages equal for MIGO / MIRO? Modification of the percentage field (VPROZ) in the PO to more than 1 decimal is not an option.
Example
    PO (quantity-based distribution, partial inv is proportional: Receive partial Qty 5 of total 12
                         Net Value            Qty              Percen           MIGO           MIRO
    Item:            9,600.00 USD    12.000 pc     100.00       4,340.00      4,340.00
    Account 1: 3,200.00 USD      4.000 pc        33.3         1,446.67      1,446.96
    Account 2: 6,400.00 USD      8.000 pc        66.7         2,893.33      2,893.04
The small difference of $0.29 for this example is inconsequential, but for larger quantieis it will have a greater impact on the account allocation.

U set or U dont set system will flag the GR non valuated once u assign multiple account assignment.
But SAP is coming up with GR valuated for Multiple account assignment in enhancement package 4.
Check out EP4 Presentation at........
https://websmp210.sap-ag.de/erp-ehp
Venkat

Logical System for Financial Accounting FI lacking; information systems

Hello,
we`ve got a problem with the creation of a SC. After the selection of a product (doesn`t matter if it`s a "free text", good or service), we got always the following Error:
"Logical System for Financial Accounting FI lacking; information systems"
I`ve already checked the attribute "ACS" in PPOMA_BBP and the RFC-Connections. Have anybody an idea, what i can do else or where i can get further information about this error (like System Log,...)?
Regards Jochen

Hi Jochen,
Kindly check the following SPRO settings in your system
1. SPROSRM ServerTech Basic settings--Define backend system for Prod category. (Ensure that your category which you are using in your SC is defined here with source/target system)
2. SPROSRM ServerCross App Basic Settings--Define Objects in backend systems. (Ensure that Purch grp, prod category, source system, and PO details are maintained here)
3. SPROSRM ServerCross App Basic Settings--Define G/L account for prod category. (Ensure that your Prod category, Source system, Acct assgnmt categry and G/L account are maintained)
Pl check the above and revert back.
Regards,
Nikhil

GL A/c numbering logic for chart of accounts BAIN

Hi,
Will any expert pl let mek now What is the GL A/c numbering logic for chart of accounts BAIN (BAIN is standard ch of A/c for India apart from CAIN)?
Regards
Anand

Your question is not clear about numbering logicu2026
First of all the GL Account # are always externally assigned (it can be either numeric and alphanumeric)
The length of GL account is 10 digits. But if you give it as 6 in TC OB13 then
u2022 Numerical account numbers
The system includes zeros to the left of the number
0000001234
u2022 Alpha-numeric account numbers
The system includes zeros to the right of the number
1131DB0000

Help for ICSS registe a B2C account

Hello All,
I want to registe a B2C account in ICSS, but even I input all fields, the button of 'submit' still can not be click. I do not know why. Are there any configuration I have not do?
It is urgent. Need for your help.

Hi Gordon,
Please follow the following note number 885866 at http://servce.sap.com/notes.
In this note it is clearly defined the solution to your problem.
Reward points if it helps.
Regards
Pranay

Script logic not working for GL account with Zero balance

Dear Experts,
I have a scenario where the GL account balance in ECC is 0 and when a script logic runs in BPC the same should capture a closing balance as "1".
Though I have written the below logic, this is not getting executed and writing back the value as "1".
Kindly help me on the same.
*WHEN ENTITY
*IS "ABC"
*WHEN ACCOUNT
*IS "20300000"
*REC(EXPRESSION = 11, ACCOUNT = 20300000,FLOW = F99, ENTITY = ABC, PROFITCENTER = 130010 , INTERCO = I_NONE , CONSOSCOPE = G_NONE, CURRENCY = LC ,CATEGORY = ACTUAL, AUDITID = INPUT)
*ENDWHEN
*ENDWHEN
*COMMIT
Regards,
Shilpa

Hello Vadim Kalinin,
Thanks for the very swift help.
Merger of the client happened in 2007. ECC is using the " 20300000- change in fair value " account to record both pre-acquisition and post-acquisition values.
Since the treatment of pre-consolidation and post consolidation reserves is different the split of the amount between pre and post-acquisition values has to be done. For the same post acquisition value is reduced from this account using a script logic as below.
WHEN FLOW
*IS "F99"
*WHEN ENTITY
*IS "ABC"
*REC(EXPRESSION = ([ACCOUNT].[20300000] -3258603),ACCOUNT = 20300000,FLOW = F99, INTERCO = I_NONE , CONSOSCOPE = G_NONE ,CURRENCY = LC ,CATEGORY = ACTUAL )
This logic worked when the account has a figure, but in July 2014 in ECC the account had a transaction and the balance has become Zero. Until this account has a figure this pre acquisition logic is not working.
For making this work, I am trying to write a new logic to make the balance of this account as "1" in BPC through the script logic.
Kindly suggest me on the same.
Regards,
Shilpa

Posting logic for stock shortage

Hi there,
I m workiing in SAP R/3 ECC 6.0 version CO module.
We are trying to find a solution for posting logic for stock shortage. Regarding this SAP Note 362037 have also been referred.
We have purchased vide PO a certain item say ferro alloy 100 kgs. @ 5000 INR each (Clearing & Forwarding charges Rs.50000 credited) at which GR was made. Now at the time of bill passing of clearing & forwarding at a later date the amount passed was Rs. 20000 when the stock quantity of ferro alloy was only 40 kgs. The system adjusted the entire Rs. 30000 with the balance inventory available reducing the inventory cost instead of transferring to Price difference account the required proportionate amount.
Whether this can be rectified in the system.
Regards,
Divraj Agarwal
Edited by: Divraj Agarwal on Feb 22, 2010 12:32 PM

Hi,
Create a Formula variable with Replacement Path for Batch, and replace with Attribute and attribute is Date OF Manufacturing, so using this you get Date Of manufacture. And next create a Formula variable with Custome Exit and select Dimenstion ID = Date.
And write the following code to get Current day.
WHEN 'ZVCURDAY'.
      CLEAR: l_s_range.
      l_s_range-low = sy-datum.
      l_s_range-sign = 'I'.
      l_s_range-opt = 'EQ'.
      APPEND l_s_range TO e_t_range.
so by using you get current date. So create Formula and do Substraction, i.e. Curday-Dateof Manufacture (above Replcement variable), so you get number of days from Manufacturing.
Then you csan create conditions, i.e. <30 days, <60 days like that.
Thanks
Reddy

No G/L account selected for Asset Account in Business Partner Master Data

Hi All,
When i tried to raise A/P invoice for an Asset Item the system is raised the following error" why?
" No G/L account is selected for Asset Account in Business Partner master data "
thanks
SV Reddy

hi Giri,
When you choose from list against the Asset Account in the business partner master data it is only displaying the Trade Creditors Account domestic and foreign acounts only. which one to choose in this case? i presume trade creditors account is the one to choose. but what is the logic for asset items to choose this Trade Creditors Account? Or else can we create a separate control account for purchasing the Asset items? what is the logic again here choosing a separate account through option create new ?
thanks
SV Reddy

Can you give a document link for script logic for NW version7??

Hi all,
    who can give a document link for script logic for nw version7??
    thanks in advance!!

Hi Sheldon,
I read through your "HOW to...Custom BADI for replicating Destination_App...." and it was great. However, Can this call also be used with WHEN/ENDWHEN statements? In the MS version, when using Destination_App, I was also able to map source accounts into the correct destination accounts as well as source E type dim to desination E type dim with the following script (the mapping to destination ID was stored as properties within the source dimensions).
*INCLUDE SYSTEM_CONSTANTS.LGL
*SELECT(%OPACCT%, "[ID]", "OPACCOUNT", " [TRF_FPA] = 'Y'")
*SKIP_DIM = COSTCTR
*ADD_DIM = BRANDS
*RENAME_DIM OPAccount = Account_F
*RENAME_DIM CATEGORY = CATEGORY_F
*RENAME_DIM ENTITY = MARKET
*RENAME_DIM DATASRC = DATATYPE
*XDIM_MEMBERSET ENTITY = %ENTITY_SET%
*XDIM_MEMBERSET CATEGORY = %CATEGORY_SET%
*XDIM_MEMBERSET TIME = %TIME_SET%
*XDIM_MEMBERSET OPACCOUNT = %OPACCT%
*DESTINATION_APP = FPA
*CLEAR_DESTINATION
*DESTINATION OPACCOUNT = %OPACCT%
*DESTINATION TIME = %TIME_SET%
*DESTINATION CATEGORY = %CATEGORY_SET%
*DESTINATION CURRENCY = LC,USD
*WHEN ENTITY
*IS %ENTITY_SET%
*REC(ENTITY=COSTCTR.FPA_MKT,OPAccount=OPAccount.Consol_FPA)
*ENDWHEN
*COMMIT
I have tried the following code in the NW version, and it won't validate. Do you know if there's a way to achieve this?
*XDIM_MEMBERSET CATEGORY<>ACTUAL
*XDIM_MEMBERSET ACCOUNTHR =BASE_ANNL_SAL,BONUS,BENEFITS_TAX
*XDIM_MEMBERSET CURRENCY=LC
*START_BADI DAPP
DESTINATION_APP=CC_PLAN
RENAME_DIM="ACCOUNTHR=ACCOUNTCC"
WRITE=OFF
*END_BADI
*WHEN ACCOUNTHR
*IS "BASE_ANNL_SAL","BONUS","BENEFITS_TAX"
*REC(ACCOUNTCC=ACCOUNTHR.CCPLANACCT)
*ENDWHEN
Regards,
Karen

Contact Type for an Account

Why 'Contact Type' is required to be entered for an Account, as we already define 'Account Type' and ideally same should be populated for a 'Contact Type' while linking a 'Contact' to 'Account'? Any specific reason ? (Scenario > I am first creating an Account & then linking Contact to an Account)

Hi Bobb,
Thx for you answer, but i am still not convinced on a contact being linked to multiple Accounts,
Lets take a scenario; i created an Account "General Electric" with Account Type = 'Customer'. I am now creating a contact for this account (from Account Detail page) named "Mr. John Miller"; logically this contact should be 'Customer' type only, as i cannot have this contact as my 'Competitor' or something else. Do you agree?

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

Invalid line of logic for RolltoBS logic

Hi all,
When I try to validate my logic file, I receive the error "invalid line in logic section: ROLLTOBS( 3116000, CALCNI, FINSTMT, PL, DEC )
I simply took this logic line from apshell and modified for my accounts. Is there anything else I need to do?
Thank you,
Jennifer

To help trouble-shoot your problem, I'll describe how ROLLTOBS works. But to cut a long story short -- you should really consider using the account transformation business rule (SPRunCalcAccount) instead of this ROLLTOBS function. It is far easier to set up, faster, more reliable, and more flexible. In periodic data storage apps, it does a wonderful job of accumulating the periodic P&L accounts to YTD B/S, without you needing to sweat all the details in messy code like the ROLLTOBS.
ROLLTOBS isn't a logic instruction by itself.
In ApShell (on 5.1 at least), it refers to a function that is located in the System_Library.lgl file. I can see that the Finance app's default logic has this ROLLTOBS commented out, but to make it work, you need the following:
*SYSLIB System_Library.lgl
// I'll explain this next line in a second...
*INCLUDE system_constants.lgl
//Move Net Income to Balance Sheet
ROLLTOBS( CYNI, CALCNI, FINSTMT, PL, DEC )
You may then have a problem if your application structure is different from ApShell. Check out the code in the system library file, which is located here:
Data\Webfolders\ApShell\SystemLibrary\Logic Library
You can see below that there are references to other functions such as ACCOUNTDIM and TIMEDIM, which must be defined somewhere for the logic to work. They are normally defined in your system_constants.lgl file, located in the same AdminApp\Application directory as the logic files themselves. Therefore, you need to include that file, too.
Also, as I look at this code now, I see the time dim memberset definition is very old syntax. I believe there are now better ways to expand scope to prior periods.
//=========================================================================================
*SUB ROLLTOBS(%bsaccount%, %workaccount%, %acctproperty%, %propertyvalue%, %LastPeriod%)
// Roll a periodic PL account to a BS account
// Requires a property to identify the PL accounts to be totaled
// Requires a temporary work account to calculate the total of the PL account
//=========================================================================================
// set the appropriate region to clear
//(current period, not prior)
*CLEAR_DESTINATION
*DESTINATION TIMEDIM=%TIME_SET%
*DESTINATION ACCOUNTDIM=%bsaccount%,%workaccount%
*WHEN ACCOUNTDIM.%acctproperty%
*IS "%propertyvalue%"
    *REC(ACCOUNTDIM=%workaccount%)
*ENDWHEN
*COMMIT
// must process one period at a time
*PROCESS_EACH_MEMBER=TIME
// enforce loading the appropriate region
*XDIM_MEMBERSET TIMEDIM=[TIMEDIM].[%TIME_SET%],strtomember("["+[TIMEDIM].[%TIME_SET%].properties("PRIOR")+"]")
*XDIM_MEMBERSET ACCOUNTDIM=%workaccount%,%bsaccount%
*WHEN ACCOUNTDIM.ID
*IS %workaccount%
*WHEN TIMEDIM.CURRENT
*IS %TIME_SET%
   *REC(ACCOUNTDIM="%bsaccount%")
*ENDWHEN
*IS %bsaccount%
*WHEN TIMEDIM.CURRENT
*IS<>%TIME_SET%
   *WHEN TIMEDIM.PERIOD
   *IS<>%LastPeriod%
    *REC(TIMEDIM="%TIME_SET%")
   *ENDWHEN
*ENDWHEN
*ENDWHEN
*COMMIT
*ENDSUB
//=========================================================================================

Need logic for invoice due date and discount due date uncear

Hi Experts.. am new to ABAP
i had an issue please need some logics for these..
Formatting of the Invoice due dates and Discount due date is unclear e.g 20101109,
Invoice due date and Discount due dates are in correct on 10 and 20 days reminders on missing credit notes for blocked invoices.
<removed by moderator>
Thanks & Regards
Edited by: Thomas Zloch on May 18, 2011 1:55 PM

Can you provide more info?
are you talking about BSID open accounts?
if yes, use function module DETERMINE_DUE_DATE.
<removed by moderator>
Edited by: Thomas Zloch on May 18, 2011 2:10 PM - please do not ask for "award"

How to create a reference user for B2C application?

Hello,
Can somebody please tell me how to create a reference user for B2C application?
I am trying to create a new account on the B2C site. It is giving me a null pointer exception. I have not created a reference user for B2C application.
Is there any documentation available to explain the steps required for this?
Thanks,
Harsha

Hi Harsha,
Please lookup http://help.sap.com/saphelp_crm40sr1/helpdata/en/be/511378ab1311d4b32b0050da4cccf0/frameset.htm for more information.
Cheers,
Ashok.

LDB for BSEG - Accounting Document

Can anybody tell me the logical database for BSEG accounting Document

BKPF Accounting document header
BSEG Accounting document segment
BSET Tax data document segment
BSEC One-time account data document segment
<b>Logical databases: BRM </b>
reward if useful
Message was edited by:
santhosh reddy

Logic for Automatice AccountID generation for B2C Accounts

Similar Messages

Maybe you are looking for