Mass Additions Transactions with FUTURE status in FA

Hello, this may have been asked before, but could someone let me know what does the status FUTURE means when going into Prepare Mass Additions? Thanks.

FUTURE would indicate that you want to add the asset in a period that is currently not open. In such cases the asset would remain in the mass additions table till the period is open. Then the process pending transactions program will add it to the current period.

Similar Messages

How to delete Pending WIP Move Transactions with running status

hello,
can any one guide me, how to delete Pending WIP Move Transactions with running status
thanks in advance
sadiq

Please refer to the following note:
Note: 105647.1 - WIP and COST Frequently Used Troubleshooting Scripts
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=105647.1

CO11 Transaction with confirmation status

hello friends,
I have a excel sheet with two field - order number and quantity to be confirmed.
i need to upload this excel file into sap system, record transaction CO11 and then call transaction.
after all this i need to download a excel file with four fields-
1)order number
2) material number
3)quantity to be confirmed
4) confirmation status.
can anybody please guide me what to be done after calling the transaction.....

Nikhil,
Try using the Database View "CRMV_INDEX_JEST". You need to pass Status to the field STAT and transaction type to the field PROCESS_TYPE.
Hope this helps.
Regards,
Shyamak.

Necessary to empty Mass-Addition Workbench before run Depreciation?

Hi!
Is it necessary to empty the Mass-Addition Transactions in Workbench before the Depreciation Run will be started or the Period will be closed?
Which impact does it have if few Transactions will remain in the Mass-Addition Workbench? Because till Depreciation - Run or Month End Closing it will be not possible to finish editing all Mass Additions Transactions.
Thank you!
kind regards
Evelyn

Hi
Answer can be both Yes and No
Case I : Say you have pending transaction for the current period in Mass Addition, then it is required to post them before running depreciation and they can't be processed later.
Case II: If you have future trsanctions in mass addition, no need to worry . when you will close the period depreciation request set will run Proces sPending Transactions and will post any elligible lines from mass addtiions
Thanks
Sunil

Sales order stuck in interface with line status shipped in transaction form

Hi All
Can anyone tell me the reason for the sales orders getting stuck in the interface with line status Shipped in the shipping transaction form.
I ran the Interface trip stop -SRS and mode All for this delivery Id. I checked the log file of it. The error showing in the log file is ORA-20001; ORA-20120 none of the Registers have Balances greater or equal to the excisable amount -> 350 or education cess amount ->7.
Please tell me the set up where to check the register balances and how to proceed with this order. can we manually update the registers if required to process this order.
Thanks in advance
Prem.

Hi,
HOLD status
This is an EOIO message whose predecessor was not processed successfully yet. The status is retained until all predecessors are delivered successfully. If a predecessor has the "System error" status and is restarted, all successors are also restarted provided that the delivery of the predecessor is successful.
If a predecessor has the "canceled with errors" status, further processing is not possible in systems before Support Package 11 for the adapter framework and Support Package 10 for the adapter framework core patch 02. In higher version systems, the status of predecessors can only be set to "canceled with errors" in a manual way. Successors that have the "Holding" status can be restarted after you have set the "canceled with errors" status (see related note 811864).
Regards,
Sreenivas

My BDOCs(transaction smw01) are all waiting with yellow status

I don't know why my BDOCs(transaction smw01) are all waiting with yellow status. Shouldn't they be automatically transfering data to my data source. If i manually process the BDOC then data goes to the datasource which can be seen via transaction RSA3. Help?

Hi Kaushal,
I am also facing the similar problem as Prakash, I don't know why my Bdocs are all waiting with yellow status in smw01.I followed your steps but in SMOHQUEUE the status of the queue demon is Hold because of this the status of Bdocs are yellow.If yes would you pls tell me the steps to turn it to green.If i manually do(Reprocess or register that queue in smqr) everything is working fine but is there any way we can turn Bdocs from yellow to green automatically.I appreciate it in advance. If you find any doc. pls fwd it to [email protected]
Thanks a lot
With Regards
Nagamani.

Mass Additions Errors

Hi,
I am trying to create/load an asset using fa_mass_additions interface by running Post Mass Additions Program
Initially i got &EXPENSE_CODE_COMBINATION_ID cannot be null and now i am getting the below error
The Location for &LOCATION cannot be NULL.
Mass Addition ID: 49701 ==> ** Failed **
Number of successes: 0
Number of failures: 1
Module Mass Additions Post ended with error
I am passing both EXPENSE_CODE_COMBINATION_ID and LOCATION_ID into fa_mass_additions interface but the trigger on it is overwriting to null
Please let me know if any one of you came across this issue.
Thanks,
Nagaraj

Hi Devidas,
1. Balance of ORD 1000010 is not zero.
For this please get in touch with Costing persons. Orders are not yet settled. hence this problem is there.
2. Unprocessed future change recs for order 1000012 prevent del. flag/completion.
Few transactions are open for this material please close it.
3. System status CRTD is active (ORD 1000220)
Please put status TECO for this orders this will solve your problem.
Please confirm,
Regards,
Amit Kulkarni.

Undelete in Mass Additions Queue=Delete

My business user inadvertently deleted all AP transactions from Mass Additions using Tools==>Delete All. The transactions were in queue 'New' but now are in queue 'delete'. Is there a way to put them in the 'New' queue again. No post process has happened as of yet. The trasactions were sent by AP using Mass Additions process.
Thanks in Advance!
mtm

Hi,
We could find the work around for deletion of assets which are in POST Status.
We edited the Description of the Asset and saved it again.This way it allowed to Delete the Mass additions which got stuck with POST status.
Thanks

Undelete Mass Additions - Queue 'delete'

My business user inadvertently deleted all AP transactions from Mass Additions using Tools==>Delete All. The transactions were in queue 'New' but now are in queue 'delete'. Is there a way to put them in the 'New' queue again. No post process has happened as of yet. The trasactions were sent by AP using Mass Additions process.
Thanks in Advance!
mtm

Hi,
We could find the work around for deletion of assets which are in POST Status.
We edited the Description of the Asset and saved it again.This way it allowed to Delete the Mass additions which got stuck with POST status.
Thanks

Date in service - AP to FA Mass addition

Hi
In R12, when we ran the AP to FA Mass addition and querying mass addition in FA, system is showing new assets with date in service as the date on which Mass addition was run. Is that the intended functionality..?
Can we change the date in service as invoice date by default through mass addition program..?
regards
Ahsan

Please check in KON* series table in SE16N transaction. I guess KOHN table may help you out. You can see other similar tables.
In any one of the table you will find validity data.

Mass addition transfer

Hello,
What are the conditions to transfer items to FA?
Is that the combination that have same category in FA?
If the line in distribution in AP is matched to PO and has an item that defined "Fixed asset" - it will transfer to FA ?
thanks,
Kobi Idah

For doing the Mass Transfer in Fixed Assets the following conditions is to be met.
a) Define the Asset Category for that Asset.
b) If it is matched to PO, then in the Charge account you need to choose the Asset Clearing Account only.
c) When the Invoice been matched to Purchase Order, make ensure from the Show->Field-> Track as Asset need to be enabled otherwise the payables distributions will not be identified as a 'Asset'.
d) Validate an Invoice
e) Account an Invoice.
f) Payable Transfer to General Ledger.- Report Need to be run.
g) Run the Report
-- Mass Addition Create
-- Mass Addition Create Report.
Navigate to Fixed Asset Module.
Go to Prepare Mass Addition.
Query with your asset book / Invoice Number.
Change the status from Queue to Post.
Go to Post Mass Addition.
Choose your Asset Book and submit the concurrent.
Make ensure these concurrents should complete Normal.
I have also mentioned the Accountign entries at different stages--
In Purchasing Module
Expense accural a/c Dr
Asset Clearing a/c.
In Payables Module
Asset Cost a/c
To Liability
In Fixed Assets Module
Asset Clearing a/c
To Asset Cost

Fa mass additions (fa_addition_pub.do_addition)

Hi All,
I am working on Mass Addition interface. After successfull execution of fa_addition_pub.do_addition package.I got asset_id too..
output :-
S 0
SUCCESS
THID 167215
ASSET_ID 109950
ASSET_NUMBER 99339
But my issue is i am not able to get this data in fa_mass_addition table ...In which table this data is updated ?
How to get the data in Fa Mass Addition so that i can run 'post mass addition' to get status as posted..?
Your knowledge will be appreciable..
Thanks
Raman Sharma

FA_ADDITIONS_B table in the FA
but will u provide the script or review mine ..
/* Formatted on 2012/05/23 14:19 (Formatter Plus v4.8.8) */
DECLARE
-- CURSOR C1
-- IS
-- SELECT *
-- FROM MCB_FA_TABLE;
P_API_VERSION NUMBER;
P_INIT_MSG_LIST VARCHAR2 (200);
P_COMMIT VARCHAR2 (200);
P_VALIDATION_LEVEL NUMBER;
X_RETURN_STATUS VARCHAR2 (200);
X_MSG_COUNT NUMBER;
X_MSG_DATA VARCHAR2 (200);
P_CALLING_FN VARCHAR2 (200);
PX_ASSET_DIST_REC FA_API_TYPES.ASSET_DIST_REC_TYPE;
PX_TRANS_REC FA_API_TYPES.TRANS_REC_TYPE;
PX_DIST_TRANS_REC FA_API_TYPES.TRANS_REC_TYPE;
PX_ASSET_HDR_REC FA_API_TYPES.ASSET_HDR_REC_TYPE;
PX_ASSET_DESC_REC FA_API_TYPES.ASSET_DESC_REC_TYPE;
PX_ASSET_TYPE_REC FA_API_TYPES.ASSET_TYPE_REC_TYPE;
PX_ASSET_CAT_REC FA_API_TYPES.ASSET_CAT_REC_TYPE;
PX_ASSET_HIERARCHY_REC FA_API_TYPES.ASSET_HIERARCHY_REC_TYPE;
PX_ASSET_FIN_REC FA_API_TYPES.ASSET_FIN_REC_TYPE;
PX_ASSET_DEPRN_REC FA_API_TYPES.ASSET_DEPRN_REC_TYPE;
PX_ASSET_DIST_TBL FA_API_TYPES.ASSET_DIST_TBL_TYPE;
PX_INV_TBL FA_API_TYPES.INV_TBL_TYPE;
LV_COUNT NUMBER := 1;
L_MESG_COUNT VARCHAR2 (2000);
L_MESG VARCHAR2 (2000);
L_RETURN_STATUS VARCHAR2 (2000);
PX_INV_RATE_TBL FA_API_TYPES.INV_RATE_TBL_TYPE;
PX_INV_REC FA_API_TYPES.INV_REC_TYPE;
PX_INV_TRANS_REC FA_API_TYPES.INV_TRANS_REC_TYPE;
BEGIN
BEGIN
FA_SRVR_MSG.INIT_SERVER_MESSAGE;
FND_MSG_PUB.INITIALIZE;
END;
P_API_VERSION := 1.0;
P_INIT_MSG_LIST := FND_API.G_FALSE;
P_COMMIT := FND_API.G_FALSE;
P_VALIDATION_LEVEL := FND_API.G_VALID_LEVEL_FULL;
X_RETURN_STATUS := L_RETURN_STATUS;
X_MSG_COUNT := L_MESG_COUNT;
X_MSG_DATA := L_MESG;
P_CALLING_FN := NULL;
PX_ASSET_DESC_REC------------------------------------------------------
PX_ASSET_DESC_REC.ASSET_NUMBER := 'XPRIA1100'; ---FA.ASSET_NUMBER;
PX_ASSET_DESC_REC.DESCRIPTION := 'Xperia Mobile'; ---FA.DESCRIPTION;
PX_ASSET_DESC_REC.ASSET_KEY_CCID := 2; ---FA.ASSET_KEY;
PX_ASSET_DESC_REC.TAG_NUMBER := NULL; ---FA.TAG_NUMBER;
PX_ASSET_DESC_REC.SERIAL_NUMBER := NULL; ---FA.SERIAL_NUMBER;
PX_ASSET_DESC_REC.MANUFACTURER_NAME := NULL; ---FA.MANUFACTURER_NAME;
PX_ASSET_DESC_REC.MODEL_NUMBER := NULL; ---FA.MODEL_NUMBER;
PX_ASSET_DESC_REC.IN_USE_FLAG := 'YES'; ---FA.IN_USE_FLAG;
PX_ASSET_DESC_REC.INVENTORIAL := 'YES'; ---FA.INVENTORIAL;
PX_ASSET_DESC_REC.OWNED_LEASED := 'OWNED'; --FA.OWNED_LEASED;
PX_ASSET_DESC_REC.NEW_USED := 'NEW'; ---FA.NEW_USED;
PX_ASSET_DESC_REC.CURRENT_UNITS := '10'; ---FA.CURRENT_UNITS;
PX_ASSET_CAT_REC-------------------------------------------------------
PX_ASSET_CAT_REC.CATEGORY_ID := 21; ---FA.CATEGORY_ID;
PX_ASSET_CAT_REC.DESC_FLEX.ATTRIBUTE1 := NULL; ---FA.ATTRIBUTE1;
PX_ASSET_CAT_REC.DESC_FLEX.ATTRIBUTE2 := NULL; ---FA.ATTRIBUTE2;
PX_ASSET_CAT_REC.DESC_FLEX.CONTEXT := 'COMPUTER-PC'; ---FA.CONTEXT;
PX_ASSET_FIN_REC.COST := 2400; ---FA.COST;
PX_ASSET_FIN_REC.ORIGINAL_COST := 2400; ---FA.ORIGINAL_COST;
PX_ASSET_FIN_REC.SALVAGE_VALUE := NULL; ---FA.SALVAGE_VALUE;
PX_ASSET_FIN_REC.DATE_PLACED_IN_SERVICE := SYSDATE; --- FA.DATE_PLACED_SRV;
PX_ASSET_FIN_REC.DEPRECIATE_FLAG := NULL; ---FA.DEP_FLAG;
PX_ASSET_FIN_REC.DEPRN_METHOD_CODE := NULL; ---FA.DEP_METHOD_CODE;
PX_ASSET_FIN_REC.LIFE_IN_MONTHS := NULL; ---FA.LIFE_IN_MONTHS;
PX_ASSET_DEPRN_REC.YTD_DEPRN := NULL; ---FA.YTD_DEP;
PX_ASSET_DEPRN_REC.DEPRN_RESERVE := NULL; ---FA.DEP_RESERVE;
PX_ASSET_HDR_REC.BOOK_TYPE_CODE := 'OPS CORP'; ---FA.BOOK_TYPE_CODE;
PX_ASSET_DIST_REC.UNITS_ASSIGNED := NULL; ---FA.UNITS_ASSIGNED;
PX_ASSET_DIST_REC.EXPENSE_CCID := NULL; ---FA.EXPENSE_CCID;
PX_ASSET_DIST_REC.LOCATION_CCID := NULL; ---FA.LOCATION_CCID;
PX_ASSET_DIST_REC.TRANSACTION_UNITS := NULL;
--PX_ASSET_DIST_REC.UNITS_ASSIGNED;
PX_ASSET_DIST_TBL (1) := PX_ASSET_DIST_REC;
PX_INV_TBL (1) := PX_INV_REC;
--l_inv_rec.source_line_id := i.source_line_id;
PX_INV_REC.FIXED_ASSETS_COST := 2400; ---I.FIXED_ASSETS_COST;
PX_INV_REC.PAYABLES_COST := 2400; ---I.PAYABLES_COST;
PX_INV_REC.PAYABLES_CODE_COMBINATION_ID := NULL;
---I.PAYABLES_CODE_COMBINATION_ID;
PX_INV_REC.INVOICE_NUMBER := NULL; ---I.INVOICE_NUMBER;
PX_INV_REC.PO_NUMBER := NULL; ---I.PO_NUMBER;
PX_INV_REC.UNREVALUED_COST := NULL; ---I.UNREVALUED_COST;
PX_INV_REC.PROJECT_ID := NULL; ---I.PROJECT_ID;
PX_INV_REC.TASK_ID := NULL; ---I.TASK_ID;
PX_INV_REC.DELETED_FLAG := 'NO'; ---I.DELETED_FLAG;
PX_INV_REC.DESCRIPTION := NULL; ---I.DESCRIPTION;
PX_INV_REC.PO_VENDOR_ID := NULL; ---I.PO_VENDOR_ID;
PX_INV_REC.AP_DISTRIBUTION_LINE_NUMBER := NULL;
---I.AP_DISTRIBUTION_LINE_NUMBER;
PX_INV_REC.PAYABLES_UNITS := NULL; ---I.PAYABLES_UNITS;
PX_INV_REC.INVOICE_ID := NULL; ---I.INVOICE_ID;
PX_INV_REC.INVOICE_DATE := NULL; ---I.INVOICE_DATE;
PX_ASSET_TYPE_REC------------------------------------------------------
PX_ASSET_TYPE_REC.ASSET_TYPE := 'CAPITALIZED'; ---FA.ASSET_TYPE;
PX_INV_TRANS_REC.TRANSACTION_TYPE := 2; ---TRANSACTION_TYPE_CODE;
-- PX_DIST_TRANS_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_TYPE_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_HIERARCHY_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_FIN_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_DEPRN_REC := NULL; Modify the code to initialize this parameter
-- PX_ASSET_DIST_TBL := NULL; Modify the code to initialize this parameter
APPS.FA_ADDITION_PUB.DO_ADDITION (P_API_VERSION
, P_INIT_MSG_LIST
, P_COMMIT
, P_VALIDATION_LEVEL
, X_RETURN_STATUS
, X_MSG_COUNT
, X_MSG_DATA
, P_CALLING_FN
, PX_TRANS_REC
, PX_DIST_TRANS_REC
, PX_ASSET_HDR_REC
, PX_ASSET_DESC_REC
, PX_ASSET_TYPE_REC
, PX_ASSET_CAT_REC
, PX_ASSET_HIERARCHY_REC
, PX_ASSET_FIN_REC
, PX_ASSET_DEPRN_REC
, PX_ASSET_DIST_TBL
, PX_INV_TBL
, PX_INV_RATE_TBL
-- END LOOP;
LV_COUNT := LV_COUNT + 1;
COMMIT;
DBMS_OUTPUT.PUT_LINE ( X_RETURN_STATUS
|| ' - '
|| X_MSG_COUNT
|| ' - '
|| X_MSG_DATA
L_MESG := 'FAILED (' || SQLERRM || '): ' || L_MESG;
END;
it returns with a message ( E - 1 - OFA )
which is not descriptive at all

My BDOCs in CRM are all waiting with yellow status

I don't know why my BDOCs(transaction smw01) are all waiting with yellow status. Shouldn't they be automatically transfering data to my data source. If i manually process the BDOC then data goes to the datasource which can be seen via transaction RSA3. Help?
Message was edited by: Prakash Singh

hi Prakash,
again oss note 692195-FAQ: Sales Analytics and CRM-BW data Extraction ?
bwa5 and bwa7, delta is activated ?
and initialization performed in bw ?
626214 619122
3. If there are queues in SMQ1 with erroneous status then activate
   these queues.
   In Transaction SMQ1 if there are Queues existing with
   names beginning with CRM_BWAn (n is number) then
   activate these queues in the same transaction.
4.a)If required activate the datasource
    Go to transaction BWA5   > select the required datasource and
    activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
  selecting the name of the datsource and pressing the candle icon for
  'activate delta'.
Symptom
There may be problems or issues related to data tranfer from CRM to BW.
Other terms
CRM-BW extraction,upload,initial,delta,full upload ,Sales Analytics,
Reason and Prerequisites
There could be errors in customization or program errors due to which
data may not be transferred or incorrectly transferred to BW.
Solution
Question 1 : The Extraction from CRM to BW takes a very long time. What
can be done? (Performance Issues)
Question 2 : On executing transaction RSA3 I get records but I find 0
records when I load data from BW request.(No Data Available).
How can I extract data in this case?
Question 3 : The Deltas for my data source are not extracted . What can
I do?
Question 4: How can I extract the fields, which are not provided in the
standard data source extraction ?
Question 5: I am unable to extract user status correctly.What should I
do?
Question 6 : What can I do when the activity/Opportunity/Complaint
reasons(Code,CodeGruppe,Katalogart) are not extracted?
Question 7: What can I do if the deleted opportunities
are not reflected in BW?
Question 8: How do I activate the metadata?
Question 9: I donot get any records for the delta upload of my attribute
datasource(s).What is to be done?
Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0
and various other BW status mean ?
Solutions
Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues)
Suggestion 1: Please implement notes 653645 (Collective note) and
639072(Parallel Processing).
The performance could be slow because of the wrong control parameters
used for packaging.
You can change the package size for the data extraction.
Also note that changing the package size in the transaction SBIW
would imply a change for all the extractors. Instead, you could
follow the path in the bw system.
Infopackage (scheduler)    > Menu 'Scheduler'   > 'DataS. default data
transfer'   > maintain the value as 1500 or 1000(This value is variable)
The package size depends on the Resources available at the customer side
(The no of parallel processes that could be assigned =
1.5 times the no of CPU's available approx.)
Question 2 : On executing transaction RSA3 I get records but I find 0
records when I load data from BW request.(No Data Available)
Suggestion 2: First check if there are any entries in the table
CRMD_ORDER_INDEX.Only if there are entries in this table you can
extract records.
If this is not the case then,
It is possible that the user does not have sufficient
authorities for extraction of the relevant objects.
Additionally, please review and implement the following notes
615670
161570
150315
618953
If you are in the release 4.0 then
To do BW extraction with the user please see that the following
authorization object exists(display mode is enough):
CRM_ACT, CRM_OPP, CRM_LEAD, CRM_SAO, CRM_SEO, CRM_CO_SE, CRM_CO_SC
CRM_CO_SA, CRM_CON_SE, CRM_CMP, CRM_ORD_OP, CRM_ORD_LP, CRM_ORD_PR
CRM_ORD_OE, CRM_CO_PU, CRM_CO_PD, CRM_ORD_PO
(all these objects are linked to transaction crmd_order).
Question 3 : The Deltas for my data source are not extracted . What can I do?
Suggestion 3: Please check the following.
Please Check if the services have been generated in transaction GNRWB.
If they are not active(not marked 'X' before their names) then activate
the services following the steps here.
Go to transaction GNRWB
Select BUS_TRANS_MSG
Select (on the right, the services) : BWA_DELTA3, BWA_FILL, BWA_queue
Press Generate.
Also check for the following:
1. The delta should have been initialized successfully.
2. Confirm that all Bdocs of type BUS_TRANS_MSG
   are processed with success in SMW01.
3. If there are queues in SMQ1 with erroneous status then activate
   these queues.
   In Transaction SMQ1 if there are Queues existing with
   names beginning with CRM_BWAn (n is number) then
   activate these queues in the same transaction.
4.a)If required activate the datasource
    Go to transaction BWA5   > select the required datasource and
    activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
selecting the name of the datsource and pressing the candle icon for
'activate delta'.
5. In BW system
   Go to transaction RSA1   > modeling   > infosources   > select the
   infosource   > right mouse click on the selected
   infosource   > choose option replicate datasource
    Activate the infosource.
6. Go to the scheduler for the infosource   > select delta in the
    update >choose the option PSA only (in the Processing tab)
    > start immediately
Check the entry in the RSA7 in the OLTP(CRM system)
Question 4: How can I extract the fields, which are not provided in the standard data source extraction .
Suggestion 4: Follow the steps mentioned below.
1. Enhance Extract Structure with the required fields. (Create & include
   an append structure to the extract structure via transaction RSA6).
2.a) Release the fields of the append for usage. ( To do this, double
   click on the Datasource and remove the flags in the column 'Hide
   Field' for all fields of Append. )
2.b)If the new fields cannot be seen in the extract structure of
    the transaction BWA1 then change and save the datasource, and then
    activate it in RSA6.
3. Define your mappings in BADI (CRM_BWA_MFLOW) to fill these fields.
Goto SPRO .
Follow the path ->
SAP Implementation guide ->Implementation with other mySAP components ->
Data transfer to the Business Information Warehouse->
Settings for the application specific datasources (CRM)->
Settings for BW adapter->
Badi :BW adapter :Enhancement of datasources in messaging flow.
4. Replicate the new Datasource to BW.
5. Expand the Communication Structure in BW.
6. Maintain transfer Rules for the new Datasource.
7. Activate the trasfer rules and perform the upload.
Question 5: I am unable to extract user status correctly.What should I
do?
Suggestion 5 :Check the following notes
531875
616062
713458
700714
765281
Question 6 : What can I do when the activity/Opportunity/Complaint
reasons(Code,CodeGruppe,Katalogart) are not extracted.
Suggestion 6 :Check the following notes
481686
516820
603609
617411
711146
Question 7:Deleted opportunities are not reflected in BW.
Suggestion 7: Check the note 706327.
Question 8: How do you activate the metadata?
Suggestion 8:CRM BW adapter meta data has to be activated first before
it is available in the system. You can use Transaction BWA5 to copy the
meta data for selected DataSources. You can reach the transaction via
the IMG maintenance 'SAP Reference IMG -> Settings for SAP Business
Information Warehouse -> Activate BW Adapter Meta Data'. For more
information, see the documentation on the IMG activity 'Activate BW
Adapter Meta Data'. (Note 432485)
Question 9: I donot get any records for the delta upload of my attribute
datasource(s).What is to be done?
Suggestion 9: In case of attribute datasources, it is possible that the
entry for the GUID is missing in the table SMOXAFLD.
If , for example the datasource 0CRM_OPPT_ATTR is not giving deltas
then you can follow the steps:
1)If Delta process is active for the attribute datasource e.g.
     0CRM_OPPT_ATTR, then stop the delta process in the BW
     system
2) In the CRM system, Make the entry in the table SMOXAFLD
   for the datasource with the Key
   as 0CRM_OPPT_ATTR     GUID 3) Save the entry.Activate the datasource                           4) Check that the above entry is replicated in smoxafld_s also    after this.               5) Create a transport request manually for the following    object             R3TR   SMO4   0CRM_OPPT_ATTR
Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0 and various other BW status mean ?
Suggestion 10: The BW status are used to extract system and user defined
status.
The BW status are defined in the customization settings in SPRO.
Check for-> Status Concept for BP/Product/CRM objects
Here goto-> Process user status You will find the documentation attached here for the user status. Going inside the transaction you will find the status groups USS0, ZIOP,ZMOP etc. The names of the various BW status are derived from this For ex. BW + ST+ One + USS0 gives the name of the field BWSTONEUSS0 or BWST + ONE + ZMOP = BWSTONEZMOP (Master opportunity values) (which means BWST + (status group name) + status object group name) Double clicking on any of the object groups will take you to the values that these status can have . For ex. BWSTONEUSS0 in your system can have values E001 ,E002,E003,E007 which will be shown in RSA3 as BW status values 1,2,3,7, respectively.
Similarly we have Goto -> Process system status (in SPRO). Here you can get the values for the system status in exactly the same way as BWSTONESYS0(Lifecycle status) , BWSTTECSYS2 (Error) etc. In RSA3 you get the names as BW status, To know which corresponds to which status here,Goto the record list in RSA3 . Here goto Settings - Layout -Current . Right click -> Press Show technical field names . You will be able to see the BW status names and will be able to adjust the layout accordingly.

To create the follow up transaction automatically on status change in sap crm?

To create the follow up transaction automatically on status change in sap crm? If yes, how to make the setting for this?

Hi vishal,
As per the requirement transaction type is activity(ACTI) & sales order(TA). when the take order objective is complete system automaticaly craete a new activity of tele sales call or metting with wholesaler.
this is requirement of client.
now i am already create all type of transaction types of activity & sales order & create follow up transaction also. i have doam already create action profile also but when i am assign this action profile to transaction & try to create an sales order no follow up transaction could be create automatically. i think the condition is not right so please help me out in this. what should be the start & schedulec condition for this scenerio

Create transaction with variant not working

Hello!
Here's my issue -- I have a program that, right now, is more of a shell than anything else. It is to access the HR Logical Database PNPCE, and to help filter the data I pull back, I created a Selection View with a couple of additional fields. I put the necessary values in these fields and saved it as a Variant.
All I want to do is create a transaction to run my program and start it using my Variant to fill in these additional fields. Using SE93, I can create a plain transaction with no problem. However, if I click the "Start with variant" drop-down field, I get a response that says screen 1000 (my default Selection Screen) has no variants.
At first we thought there was some client-side things needing configuration, but if I go create a quick-and-dirty program with a single Selection Screen value (no Selection View) and a Variant, SE93 sees the variant with no problems. So I'm wondering if maybe it has something to do with the fact that I'm using a Selection View. Unfortunately, I'm so new to ABAP, I'm completely stuck on how to proceed.
Any suggestions? Thank you so much!

Saquib, thank you SO much! You're right -- that worked.
As a relative newbie to SAP R/3 and ABAP, I'm new to little quirks like this. In other examples, the list (F4) does show the variants. For some reason, this one didn't. I entered it anyway, saved, and ran the transaction, and it popped up with the fields populated from the variant.
Again, kudos and thank you so much. Points duly awarded.

Mass Additions Transactions with FUTURE status in FA

Similar Messages

Maybe you are looking for