Field in Append Structure for Generic Datasource

Hi:
I created a Generic Datasource based on a view. After that, I created an Append to the Extraction Structure to include a field not originally on the view (and not related to any table in the view) to be calculated using customer exit in CMOD.
At the moment of activating the Datasource, this new field doesn't appear in the selection window but in RSA6 it shows there with options "Hide Field" and "Field only Known in Customer Exit" checked.
Again, I try to edit the Datasource but this field is not in the list to change those two checks.
Any idea?
Thanks.
Luis Sales

Dear Luis Sales,
I was having the same requirement. I tried it hard for removing the tick mark on the HIDE option. But it was not working at all.
I tried these steps.
1. From RSO2 went to Extract structure. Edit Mode-> append structure.
2. Appended required fields and activated both append structure and extract structure.
3. Back to datasource and Save it.
4. Came out of transaction RSO2. ( latter Logged of system )
5. after re login - RSA6 selected given Datasource and change. there I could change the selection of HIDE field. ( Even earlier I was not able to do that)
May be these steps help you out.

Similar Messages

BI : Datasource 0FI_GL_4 , Fields in Append structure

Hi Experts,
I have done extraction for 0FI_GL_4 which contains standard fields. I have appended the structure in 0FI_GL_4 and added the below two fields with description:
USNAME : User Name:
UBHKT : G/L Account Number for Our Bank Account / Bank Sub-Account.
I am going to use customer exit Exit_SAPLRSAP_001 and created Project in CMOD. I need to write the code in it, but I wanted to know as to from which table should I populate the data for fields USNAME & UBHKT. Kindly advise.
is there any single table from which i can fetch both the fields ?? Kindly advise.
Thanks & regards,
M.S
Edited by: M.S on Feb 11, 2010 12:01 PM

I would advise you not to use cmod for the fi_gl_4 extractor - there is a std BW user exit provided called BTE 5021 inside the extractor already for that purpose - have a look at OSS 410799 for info on how to use it
However - for the usnam you do not need to cmod or BTE anything - just put them exactly as the are in the user append structure ci_bsisfor the datasource - do not prefix them with a ZZ or a Y as you would normally do
Those fields exist on bkpf
The extractor does a move corresponding on and will automatically copy the field contents with no coding at all
I havent tried it for some time with bkpf records so it may or not work - if it doesnt use the BTE 5021 to read the data
With regards to the UBHKT I am slightly confused - this will always be the saknr on the bseg record (which you already have in BW on the extractor (0glaccount) for those postings to gl bank accounts.. we will need more functiona linput as to why they want it and in what circumstance

How to set Non Cumulative Init flag for Generic datasource

Hi all,
I need to create a generic datasource which can be used to initialize the Non Cumulative Cube. Eg. setting the opening balance.
The STOCKUPD field in the ROOSOURCE should be set to X so that the infopackage will have the "Generate Initial Status" option. But there is no interface available in R/3 pluggin to do this.
How can this be done? Or is it not allowed for generic datasources as it is only valid of 2LIS_03_BX datasource
for stock updation.
Will there be other issues if I change the table entry for STOCKUPD in roosource table for my datasource?
regs
Anoop

Hello,
any idea on this?
regs
Anoop

How to set Generic Delta for Generic Datasource

Hi to all,
please can any one explain me the generic Delta option for Generic datasource
after creating generic datasource, i need to set the generic delta .
can any one explain me all generic delta option in simple language with example.
Field Nm
Time samp
calend. Day
Numeric Pointer
Safety Interval Upper Limit
Safety Interval Lower Limit
New status for changed Records
Additive Delta
i shall be thankful to you for this.
Regards
Pavneet Rana

this question has been answered a million times.
search the forum.
M.

How to find where the code for append structures for LIS extractors?

Hi,
I found 4 append structures for extractor 2LIS_03_BF,
Out of 4 append structures, I found code for one, using where-used option. But in vain for other 3. Is it possible they didn't transport the code for remaining structures? how to find that?
Cheers,
Kannan N

Kannan,
When ever you apply a logic to populate tdata for the appended filed then you will be writing some code in CMOD transaction code where you will find a ZXRSAU01
program, just double click on that then it will take you to the complete exit. Ther you can find with your data source name.
Hope it helps...
****Assign Points if it helps******
Gattu

Append Structure for Table

Hi All,
I have added an append structure to a table in SE11. While adding the append structure i opened the table in display mode and added the append structure. I have also activated the append structure.
But in my transport request i can only see the append structure and not the original table. Is it safe to transport such a request ?

Hello,
When you're APPEND'ing a table you're not modifying the original table.
You are linking the APPEND structure to the original table & the linkage is maintained in the APPEND structure(see the "Attributes" tab of the APPEND structure).
Yes, the original table gets activated & adjusted when you activate the APPEND structure but it won't ask you for a TR. Whenever the TR is imported to the subsequent system the original table will automatically get activated & adjusted.
Hope i'm clear. You can read the F1 documentation on APPEND structures for further info.
BR,
Suhas

Delta-Specific Field for Generic DataSource

Hi,
I have defined a Generic DataSource for Transaction data on R/3-Side.
This DataSource is based on View/Table EKKO (Purchasing Document Header) for some specific customer requirements. Delta-Specific Field is AEDAT (Calend. Day). Safety Interval Upper Limit is set 1 Cal. Days. No Safety Interval Lower Limit has been defined. "New Status for Changed Records" has been marked.
When we see this DataSource in Extractor Checker (RSA3), this data source
Extracted all delta data where AEDAT is not blank.
When I see the content of table EKKO, I can find few records where AEDAT is blank.
These records are missing in Extractor Checker.
How I can solve this problem? Which delta-specific field can be used in
this generic Datasource? Should I define an additional Generic DataSource with
Delta-Specific Field BEDAT (as BEDAT is filled when AEDAT is blank in table EKKO)?
Thanks for the answer.

Delta based on calday wont pick all the records which are recently posted and you can not run the delta more than one time in a day ,end of the day only you can run the delta.
Set the delta as Tme Stamp and specify the Upper limit to 5 minuts.
We can run the delta no. times and pick the documents posted in short interval of time.
With Regards,
Kishore.

EEWB - In BP, adding a new field regenerates append structure

Hello,
After adding or deleting a field using EEWB, I have the following issues -
1. The new append structure that was created for BUT000 gets regenerated
2. Field labels get overwritten by field names
3. The order in which the fields were seen on the screen gets altered
Is this a known behavior of EEWB? How to alleviate this?
Thanks!

Thanks for your input Satish!
I searched using the application component suggested and the keyword and it was not very useful.
Some more details -
I created some new fields using EEWB. When you go to transaction BP, the standard tabs are displayed - ex - address, bank data, notes, etc. But now there is a new tab - Customer Data that has my custom fields on it.
In the backend, SAP has created an extend structure for table BUT000 that has these fields in it.
When I go to this extend structure, my fields are there with a ZZ prefix - Ex: ZZFIELD1, ZZFIELD2, etc. If you go to the details of these fields in data dict - transaction SE11, the Field labels - Short, Medium, Long and Heading are the same as the field names. Ex: in the first case, the four field labels will be - ZZFIELD1. I then changed the field labels to something meaningful - Ex: Renter name and rental date. After generating the structure, these labels are then displayed on the Customer data tab. So far so good.
However if I add a new field - ZZFIELD3, then all the label names that I had given (Ex: Renter name and rental date) get erased and replaced by the fieldnames again.
Also the order in which the fields were diplayed gets altered. Ex: earlier the Customer data screen was showing - ZZFIELD1, ZZFIELD2. Now it shows - ZZFIELD3, ZZFIELD2, ZZFIELD1.
I hope I have explained this issue.

Horizontal Bar in the RSA3 is not showing up for Generic Datasource.

Hi There,
Created a Generic Extarctor based on a two tables PAYR and REGUH.
Included 60 fields in the Generic datasource. Everything is fine and when i check the data in extract checker
RSA3, the horizontal bar is not showing up and i could only see 15 fields. I couldn't able to see the rest of the fields.
Can someone suggest what should i do to see all the fields in RSA3? Why Horizontal bar is not showing up?
Out of 60 fields only very few are hidden and it should show atleast 40 fields, but not happening..
Thanks
Vandana

HI There,
Thanks for all your responses.
1 - Tried to change the layout by going into Menu Settings --> Layout ---> Current, but no option to change.
2 - If I check the value of a particular field in the magnifier, then I could able to see all the fields
3 - After executing the RSA3, tried to change to ALV Grid by going into LIST, but again no option available to change.
4 - Checked the RSA2, and to my surprise all the fields are ticked as Key. Is that something why i'm able to see all fields in
     the browser?
5 - But when the check the datasource in RSA6, only 3 were ticked as Key and those three fields i can see before
     extracting the data using extract checker RSA3.
6 - Why all fields are ticked and showing and Key in RSA2 ?
The above is the current status of this issue. Can anyone please suggest how i should go head?
Thanks
Vandana

Modify fields in Append Structure

Hi there,
I am driving crazy about append structures. We appended a few fields to KNA1 - e.g. a field that keeps a version number (every time a record changes we want to increment the version starting with 1 at creation time).
We found a lot of material about how to append structures and actually, it's fairly simple to extend KNA1 with append structures. But HOW can someone update those fields?
We tried user exit EXIT_SAPLVV01_001 and BAdI IF_EX_CUSTOMER_ADD_DATA-SAVE_DATA to populate those fields at commit of customer data. In both scenarios, we don't have CHANGING or EXPORTING parameters. So, we tried to update the table directly, e.g.
method IF_EX_CUSTOMER_ADD_DATA~SAVE_DATA .
DATA: w_kna1 type kna1.
select single *
from kna1 " Customer master table
into w_kna1
where kunnr = I_KUNNR.
w_kna1-sap_version = w_kna1-sap_version + 10.
update kna1 from w_kna1.
break-point.
endmethod.
Now, when we execute VD02 the program stops at the given break-point and we see the data changed in KNA1. But the record gets updated by the SAP program SAPMF02D (underlying program of VD02), of course as we cannot manipulate the KNA1 record in the internal table of SAPMF02D.
Is there any way to store information into append structures at save time (within the same transaction) without customizing standard programs?
Many thanks for your help

Hi Maic,
Normally for append structures to standard tables, code is written in user exits where it is mandatory to change existing SAP objects (user exits exist are provided by SAP and you need change key).
For additional functionality to the existing flow of transaction, we use BADIs and customer exits (through CMOD).
Your requirement suits the first point above.
Annyways, try using method GET_DATA in badi CUSTOMER_ADD_DATA_CS. This has changing parameter for KNA1.
Ramesh.

Getting Error in Append Structure for Standard

Hi all,
Here i want to Append Structure in table RFPOS so i done all procedure . in this i have four field like ZZKUNNR , ZZNAMED , ZZLIFNR, ZZNAMEK. But when i active this structure this time i get error like
"Field name INDEX is reserved (Do not use structure as include in DB table)"
and
"Field name ORDER is reserved (Do not use structure as include in DB table)"
BUT structure is activated . now i can see my change in fbl3n T-code so i get proper change in this.
But when i transport a request in Quality this time i am not getting same output which i get in Development .
And yes request is transported with warning (YELLOW SIGN). So is it possible for this warning i am not geeting my proper output in FBL3N.
Please kindly help me out
Thanks
Keyur

Hello,
Did you do anything else also that you might have missed to mention here?
For example, was your Append structure already present in the table RFPOS & you deleted some of the fields & inserted the new ones. In this case, you might have to activate the table from database utility (transaction SE14).
If this is an append structure & if it was pre-existing (not created by you), then this structure might already had been assigned to any other table. In such a case, system will not allow you to directly assign it to a different table. You may have to first assign it to an INCLUDE structure.
Also, as you described, it indicates that there might be some problem with the fields named INDEX & ORDER. Try checking for it.
May be you should check with your BASIS guy if the transport was successful & if not, the error description.
Also, try checking the quality system for your changes.
Hope that helps you in getting some direction.
Let me know if that work out for you or not.
Regards,
Saurabh

Business scenarios on SD and MM modules for generic datasources and enhance

Hi,
Can anybody send some documents on SD and MM module on generic datasource and on enhancements.Pl send it to my MailID:[email protected]
Thanks,
Chinna

Hi,
MM Process flow:
The typical procurement cycle for a service or material consists of the following phases:
1. Determination of Requirements
Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
2. Source Determination
The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
3. Vendor Selection and Comparison of Quotations
The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
4. Purchase Order Processing
The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
5. Purchase Order Follow-Up
The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
6. Goods Receiving and Inventory Management
Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.
7. Invoice Verification
The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.
Common Tables used by SAP MM:
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
Transaction Codes:
RFQ to Vendor - ME41
Raising Quotation - ME47
Comparison of Price - ME49
Creation of PO - ME21N
Goods Receipt - MIGO
Invoice (Bill PAssing) - MIRO
Goods Issue - MB1A
Physical Inventory - MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)
Also please check this links.
http://www.sapgenie.com/sapfunc/mm.htm
http://www.sap-basis-abap.com/sapmm.htm
SD Process Flow:
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Transaction Codes:
Inquiry - VA11/VA12/VA13
Quotation - VA21/VA22/VA23
Sales Order - VA01/VA02/VA03
Delivery - VL01N/VL02N/VL03N
Billing/Invoicing - VF01/VF02/VF03
Also please check this links.
http://www.sapgenie.com/sapfunc/sd.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sapgenie.com/abap/tables_sd.htm
Production Planning:
For example, consider a pump manufacturing plant, based on the customer requirement, planning is done for future months ( we plan for a qty on particular
date). Pump is an assembly - were main component would be manufactured in the plant and others would be procured. As PP, we are concerned only in the inhouse
manufacturing but the final assembly (considering BOM) can be done only if the procured components are available. MRP helps in planning the shortage, on
particular date based on the planned date. Work center (ex. lathe) place the components are machined/assembled (were the operation is done). Sequence of
operation is routing (lead time scheduling data is got from routing). In the MRP Run,basic or lead time scheduling (need to know when to start/finish date)
is done. On creation of the production order, system checks for which BOM and routing to be picked up (if there are many routings or BOM for that particular
finished product). Availabilty checks for material,PRT and capacity needs to be done. on release of the order, confirmation of the order can be done (on
completion of the order or after manufacturing the quantities). GI and GR have to be done.PP flow ends here
step 1: creation of master data (Material master,BOM,Work center,Routing)
step 2: Planning - can be done by Planned independent requirement (MD61), Independent requirement (MD81).
we plan for a quantity, on which date (it would be finish date).
step 3: MD04 -stock/requirement lsit (plan made can be viewed in MD04)
step 4: MRP run - MD02, PIR is converted into Planned order
step 5:Planned order to be converted production order - CO40, CO41
step 6: production order to be released - CA02
step 7: confirm the production order (order confirmation-CO15 (after which GI and GR is done)
assign pts if helpful...

Extractor Checker: How to see fields in APPEND structure?

Hi Experts
I have added a new field to a datasource (0CUSTOMER_ATTR). My logic is in place in include ZXRSAU02.
I run the Extractor Checker and then check the result list to see that my logic is working. However.. i can't find a way to view all of the fields in the datasource. The Display List button shows a select range of fields (not even all of the standard structure), and unlike SE16, there doesn't seem to be a way to customise the list view to see the fields that I'm interested in (especially my appended field). I've tried all the menu options..
Does anyone know a way to do this? Without seeing the field in the result, i can't verify my changes in the checker.
thanks
tony

There is one button called current looks like variant click on it in RSA3 display.
You will be able to hide or display fields.
Hope this helps.
Edited by: Praveen G on Oct 10, 2008 3:14 AM

Append Structure for Service Orders

Dear Expert
I would like to add the "changed by" field in the General Data Tab of Service Order.
For that, I appended the following structures: CRMT_BSP_SRV_OIC_SRCHRES and CRMT_BSP_SRV_SEARCH with the cahnged_by field as defined in CRMD_ORDERADM_H.
After that, I was able to add this field in the field group and generate the layout successfully. Now this field is displayed within PCUI but not populated.
What is missing?
Thanks in advance for your help
Best regards
Stephanie

Hi Stephanie,
You have to populate the field in the Model access class associated with the screen.
Reward if helpful.
Regards,
Naveen

Unable to activate Transfer Structure for Generated Datasource in BW3.5

HI Experts,
We have a scenario where the data needs to moved from DSO A to Cube B
we have clicked the Export datasource and created 8(ODS A)
when created IP for this it gave us all selection in selection screen but we required only 3 Characters
 so we maintained the export datasource and saved it when we again tried to generate datasource it went to short dump
 with following messages:
 Short text of error message:
 Serious internal error: 
 <h4> Transfer structure got deactivated and we are unable to activate it again even by RS_TRANSTRU_ACTIVATE_ALL 
</h2>
 
 Technical information about the message:
 Diagnosis
 A serious internal error occurred. It could not be corrected.
 Procedure
 The following information is available on this error:
 1.
 2.
 3.
 4. OSS note
 Check the OSS for corresponding notes and create a new problem
 message if necessary.
 Message classe...... "RSAR"
 Number.............. 001
 Variable 1.......... " "
 Variable 2.......... " "
 Source Code Extract
 Line SourceCde
 514 IF g_subrc NE 0.
 515 MESSAGE x001.
 516 ENDIF.
 517 * Check new version neccessary
 518 l_curr_version = c_s_is_admin-odsversion.
 519
 520 IF l_new_version EQ rs_c_true.
 521 IF i_without_versioning EQ rs_c_true.
 522 MESSAGE e023 WITH c_s_is_admin-odsname_tech
 523 c_s_is_admin-isource
 524 RAISING no_psa_version_allowed.
 525 * ELSEIF i_without_versioning EQ 'C' AND
 526 * i_without_transport EQ rs_c_true.
 527 *-- special handling for migration.
 528 *- current system is target system no transport request
 529 *- necessary if a new version is needed
 530 ELSEIF i_without_versioning EQ 'C' AND
 531 i_without_transport EQ rs_c_false.
 532 RAISE inconsistency.
 533 ENDIF. .
 534
 535 IF i_objtype = rsa_c_istype-data.
 536 * check type of InfoSource first
 537 SELECT SINGLE issrctype FROM rsis
 538 INTO l_isrctype
 539 WHERE isource = c_s_is_admin-isource
 540 AND objvers = rs_c_objvers-active.
 541 IF sy-subrc <> 0 OR l_isrctype = rsarc_c_issrctype-ods.
 542 * if generated ODS InfoSource,
 543 * no PSA versioning possible
 >>>> MESSAGE x001.
 545 ENDIF.
 546 ENDIF.
 547 l_next_version = l_curr_version + 1.
 548 c_s_is_admin-odsversion = l_next_version.
 549 l_transtru_odsname+13(3) = l_next_version.
 550 * Don't use old progname but create new one
 551 CLEAR l_progname_ods.
 552 ELSE.
 553 l_next_version = l_curr_version.
 554 ENDIF.
 555
 556 ENDIF.
 557 * set transtru_names for IDoc
 558 c_s_is_admin-odsname = i_transtru_name.
 559 c_s_is_admin-odsname_tech = l_transtru_odsname.
 560 WHEN OTHERS.
 561 ENDCASE.
 562
Edited by: Sachin Shankarrao Dehey on Oct 20, 2010 8:59 AM
Edited by: Sachin Shankarrao Dehey on Oct 20, 2010 9:03 AM

Hi,
Delete all the DS and try creating from starting, to export DS, with correct selections, and then Activate the Transfer Structure..
Hope Helps,
Regards,
Laj

Field in Append Structure for Generic Datasource

Similar Messages

Maybe you are looking for