Adding a new field to an existing BDoc.

I posted this message in other forum, but I think the correct one is this.
I need to add a new field to bdoc BUS_TRANSACTION_MESSAGE, so I've added a field to structure BAD_BUS_TRANSN_MESSAGE, to the substructure PRODUCT_I.
What I need to know is how to give value to this field.
Thank you in advance.

The below page from the SAP Online help should direct you.
http://help.sap.com/saphelp_crm50/helpdata/en/25/dd90dac2584cdda1d00200b41c03a5/frameset.htm
Regards,
Gervase

Similar Messages

Adding a new Field to an existing report

Hi all,
Can anybody tell me, how to add an extra field in existing
report, without changing the basic calulation, which i made
in the same report.
Regards
Hema

okay... that is not a standard program.
sombody developed it.following is my existing code, here in last column i want to add BOM(mast-stlnr) and Component(stpo-idnrk). remaining things are okay.
REPORT ZPOTREND NO STANDARD PAGE HEADING
                  LINE-SIZE 195
                  LINE-COUNT 60(3)
                  MESSAGE-ID Z1.
TABLES: EKBE,
        MARA,
        TCURR.
SELECT-OPTIONS: S_GJAHR FOR EKBE-GJAHR,
                S_BUDAT FOR EKBE-BUDAT DEFAULT SY-DATUM NO-EXTENSION,
                S_MATNR FOR EKBE-MATNR,
                S_WERKS FOR EKBE-WERKS DEFAULT 'CE',
                S_MTART FOR MARA-MTART.
PARAMETERS: X_APP_L TYPE P DECIMALS 2 NO-DISPLAY,
            X_APP_H TYPE P DECIMALS 2 NO-DISPLAY,
            X_DTL   AS CHECKBOX.
DATA: BEGIN OF I_EKBE OCCURS 0,
      BUDAT LIKE EKBE-BUDAT,
      MENGE LIKE EKBE-MENGE,
      DMBTR LIKE EKBE-DMBTR,
      SHKZG LIKE EKBE-SHKZG,
      EBELN LIKE EKBE-EBELN,
      MATNR LIKE EKBE-MATNR,
      WERKS LIKE EKBE-WERKS,
      MTART LIKE MARA-MTART,
      MEINS LIKE MARA-MEINS,
END OF I_EKBE.
DATA: P_EBELN LIKE EKBE-EBELN,
      P_MATNR LIKE EKBE-MATNR,
      P_WERKS LIKE EKBE-WERKS,
      P_MTART LIKE MARA-MTART,
      P_MEINS LIKE MARA-MEINS.
DATA: BEGIN OF YMTH OCCURS 10,
      YYMM(6),
      MTH(3),
      COL TYPE I,
      MENGE LIKE EKBE-MENGE,
      DMBTR LIKE EKBE-DMBTR,
END OF YMTH.
DATA: S_YMTH LIKE YMTH OCCURS 10 WITH HEADER LINE.
DATA: W_YMTH LIKE YMTH OCCURS 10 WITH HEADER LINE.
DATA: G_YMTH LIKE YMTH OCCURS 10 WITH HEADER LINE.
DATA: S_FLAG.                                               "MTART FLAG
DATA: BEGIN OF CDATE,
      YYMM(6),
      DD(2) VALUE '01',
END OF CDATE.
DATA: SDATE LIKE SY-DATUM.
DATA: CMTH(6),
      PMTH(6),
      LMTH1(6),
      LMTH2(6),
      MTH(2).
DATA: W_MENGE LIKE EKBE-MENGE,
      W_DMBTR LIKE EKBE-DMBTR,
      W_MENGE1 LIKE EKBE-MENGE,
      W_DMBTR1 LIKE EKBE-DMBTR,
      W_TOTAL TYPE P DECIMALS 2,
      W_COL TYPE I,
      WTEXT(18),
      APP TYPE P DECIMALS 4,
      APP1 TYPE P DECIMALS 4,
      APP2 TYPE P DECIMALS 4.
PERFORM GET_YMTH.
SELECT P~BUDAT P~MENGE P~DMBTR P~SHKZG P~EBELN P~MATNR P~WERKS
       Q~MTART Q~MEINS
       INTO TABLE I_EKBE
         FROM EKBE AS P INNER JOIN MARA AS Q
       ON P~MATNR = Q~MATNR
       WHERE P~GJAHR IN S_GJAHR
         AND P~BUDAT IN S_BUDAT
         AND P~MATNR IN S_MATNR
         AND P~WERKS IN S_WERKS
         AND P~BEWTP = 'E'
         AND Q~MTART IN S_MTART.
FORMAT INTENSIFIED OFF.
IF X_DTL <> 'X'.
   LOOP AT I_EKBE.
      I_EKBE-EBELN = SPACE.
      MODIFY I_EKBE.
   ENDLOOP.
ENDIF.
SORT I_EKBE BY WERKS MTART MATNR EBELN BUDAT.
LOOP AT I_EKBE.
CMTH = I_EKBE-BUDAT(6).
IF P_WERKS IS INITIAL.
    P_WERKS = I_EKBE-WERKS.
    P_MTART = I_EKBE-MTART.
    P_MATNR = I_EKBE-MATNR.
    P_EBELN = I_EKBE-EBELN.
    P_MEINS = I_EKBE-MEINS.
    PMTH = CMTH.
ENDIF.
IF P_WERKS NE I_EKBE-WERKS.
    PERFORM CHG_MTH.
    PERFORM CHG_MATNR.
    PERFORM CHG_MTART.
    PERFORM CHG_WERKS.
ENDIF.
IF P_MTART NE I_EKBE-MTART.
    PERFORM CHG_MTH.
    PERFORM CHG_MATNR.
    PERFORM CHG_MTART.
ENDIF.
IF P_MATNR NE I_EKBE-MATNR.
    PERFORM CHG_MTH.
    PERFORM CHG_MATNR.
ENDIF.
IF P_EBELN NE I_EKBE-EBELN.
    PERFORM CHG_MTH.
    PERFORM CHG_MATNR.
ENDIF.
IF PMTH NE CMTH.
    PERFORM CHG_MTH.
ENDIF.
IF I_EKBE-SHKZG = 'H'.
    I_EKBE-MENGE = I_EKBE-MENGE * -1.
    I_EKBE-DMBTR = I_EKBE-DMBTR * -1.
ENDIF.
IF I_EKBE-DMBTR NE 0.
    W_MENGE = W_MENGE + I_EKBE-MENGE.
    W_DMBTR = W_DMBTR + I_EKBE-DMBTR.
ENDIF.
ENDLOOP.
PERFORM CHG_MTH.
PERFORM CHG_MATNR.
PERFORM CHG_MTART.
PERFORM CHG_WERKS.
TOP-OF-PAGE.
WRITE:/ SY-DATUM,SY-UZEIT,
          77 'A M T E K   E N G I N E E R I N G   L T D',
          180 'Page', (4) SY-PAGNO.
WRITE: / SY-REPID,
          77 '     Purchase Price Trending Report      ',
          180 SY-UNAME.
write: /78 'From Date', S_BUDAT-LOW, 'To Date', S_BUDAT-HIGH.
SKIP.
WRITE: / 'SBU :', I_EKBE-WERKS,
           '     Material Type :', I_EKBE-MTART.
SKIP.
READ TABLE YMTH WITH KEY YYMM = '999901'.
IF SY-SUBRC EQ 0.
    WRITE AT YMTH-COL ' APP Change'.
ENDIF.
WRITE: /01 'Part No',
          19 'PO No',
          31 'Curr'.
LOOP AT YMTH.
    YMTH-COL = YMTH-COL + 3.
    IF YMTH-YYMM NE '999901'.
      WRITE AT YMTH-COL YMTH-YYMM(4).
      WRITE YMTH-MTH.
    ELSE.
      WRITE AT YMTH-COL '       %'.
    ENDIF.
ENDLOOP.
ULINE.
*&      Form get_ymth
      text
--> p1        text
<-- p2        text
FORM GET_YMTH.
CMTH = S_BUDAT-HIGH(6).
PMTH = S_BUDAT-LOW(6).
IF S_BUDAT-HIGH IS INITIAL.
    CMTH = PMTH.
ELSEIF S_BUDAT-LOW IS INITIAL.
    PMTH = CMTH.
ENDIF.
LMTH1 = CMTH.
CDATE-YYMM = CMTH.
SDATE = CDATE.
SDATE = SDATE - 1.
LMTH2 = SDATE(6).
WHILE PMTH <= CMTH.
    MTH = CMTH+4(2).
    CDATE-YYMM = CMTH.
    YMTH-YYMM = CMTH.
    PERFORM GET_MTH.
    APPEND YMTH.
    SDATE = CDATE.
    SDATE = SDATE - 1.
    CMTH = sdate(6).
ENDWHILE.
YMTH-YYMM = '999901'.
YMTH-MTH = ' % '.
APPEND YMTH.
SORT YMTH BY YYMM.
W_COL = 21.
LOOP AT YMTH.
    W_COL = W_COL + 15.
    YMTH-COL = W_COL.
    MODIFY YMTH.
ENDLOOP.
APPEND LINES OF YMTH TO S_YMTH.
APPEND LINES OF YMTH TO W_YMTH.
APPEND LINES OF YMTH TO G_YMTH.
REFRESH YMTH.
APPEND LINES OF S_YMTH TO YMTH.
ENDFORM.                                                    " get_ymth
*&      Form get_mth
      text
--> p1        text
<-- p2        text
FORM GET_MTH.
CASE MTH.
    WHEN '01'.
      YMTH-MTH = 'Jan'.
    WHEN '02'.
      YMTH-MTH = 'Feb'.
    WHEN '03'.
      YMTH-MTH = 'Mar'.
    WHEN '04'.
      YMTH-MTH = 'Apr'.
    WHEN '05'.
      YMTH-MTH = 'May'.
    WHEN '06'.
      YMTH-MTH = 'Jun'.
    WHEN '07'.
      YMTH-MTH = 'Jul'.
    WHEN '08'.
      YMTH-MTH = 'Aug'.
    WHEN '09'.
      YMTH-MTH = 'Sep'.
    WHEN '10'.
      YMTH-MTH = 'Oct'.
    WHEN '11'.
      YMTH-MTH = 'Nov'.
    WHEN '12'.
      YMTH-MTH = 'Dec'.
ENDCASE.
ENDFORM.                                                    " get_mth
*&      Form chg_matnr
      text
--> p1        text
<-- p2        text
FORM CHG_MATNR.
CLEAR W_TOTAL.
LOOP AT YMTH.
    W_TOTAL = W_TOTAL + YMTH-DMBTR.
ENDLOOP.
IF W_TOTAL = 0.
    EXIT.
ENDIF.
CLEAR: W_DMBTR, W_MENGE, W_DMBTR1, W_MENGE1, APP, APP1, APP2.
READ TABLE YMTH WITH KEY YYMM = LMTH2.
IF SY-SUBRC EQ 0 AND
     YMTH-MENGE NE 0.
    W_DMBTR = YMTH-DMBTR.
    W_MENGE = YMTH-MENGE.
    READ TABLE YMTH WITH KEY YYMM = LMTH1.
    IF SY-SUBRC EQ 0.
      APP = W_DMBTR / W_MENGE.
      APP1 = YMTH-DMBTR / YMTH-MENGE.
      APP2 = ( APP1 - APP ) / APP * 100.
    ENDIF.
ENDIF.
IF X_APP_L IS INITIAL AND
     X_APP_H IS INITIAL.
ELSE.
    IF APP2 < X_APP_L OR
       APP2 > X_APP_H.
      EXIT.
      CLEAR: W_DMBTR, W_MENGE, APP.
      P_MATNR = I_EKBE-MATNR.
      P_EBELN = I_EKBE-EBELN.
      PERFORM CLR_YMTH.
    ENDIF.
ENDIF.
SKIP.
WRITE:/ P_MATNR, ' Amount ',
         'USD'.
LOOP AT YMTH.
   WRITE AT YMTH-COL(12) YMTH-DMBTR NO-ZERO.
ENDLOOP.
WRITE:/(18) ' ', ' Quantity',
        P_MEINS.
LOOP AT YMTH.
   WRITE AT YMTH-COL(12) YMTH-MENGE NO-ZERO.
ENDLOOP.
WRITE:/ P_MATNR(18), P_EBELN, 'USD' UNDER 'Curr'.
LOOP AT YMTH.
    IF YMTH-YYMM NE '999901'.
      CLEAR APP.
      IF Ymth-menge ne 0.
        APP = YMTH-DMBTR / YMTH-MENGE.
      ENDIF.
      WRITE AT YMTH-COL(12) APP.
      READ TABLE S_YMTH WITH KEY YYMM = YMTH-YYMM.
      IF SY-SUBRC EQ 0.
        S_YMTH-MENGE = S_YMTH-MENGE + YMTH-MENGE.
        S_YMTH-DMBTR = S_YMTH-DMBTR + YMTH-DMBTR.
        MODIFY S_YMTH INDEX SY-TABIX.
      ENDIF.
      READ TABLE W_YMTH WITH KEY YYMM = YMTH-YYMM.
      IF SY-SUBRC EQ 0.
        W_YMTH-MENGE = W_YMTH-MENGE + YMTH-MENGE.
        W_YMTH-DMBTR = W_YMTH-DMBTR + YMTH-DMBTR.
        MODIFY W_YMTH INDEX SY-TABIX.
      ENDIF.
    ELSE.
      WRITE AT YMTH-COL(12) APP2.
    ENDIF.
ENDLOOP.
CLEAR: W_DMBTR, W_MENGE, APP.
P_MATNR = I_EKBE-MATNR.
P_EBELN = I_EKBE-EBELN.
PERFORM CLR_YMTH.
ENDFORM.                                                    " chg_matnr
*&      Form chg_mtart
      text
--> p1        text
<-- p2        text
FORM CHG_MTART.
SKIP.
ULINE.
CONCATENATE P_MTART 'Total' INTO WTEXT SEPARATED BY SPACE.
PERFORM PRN_TOT TABLES S_YMTH.
P_MTART = I_EKBE-MTART.
LOOP AT S_YMTH.
    CLEAR: S_YMTH-DMBTR, S_YMTH-MENGE.
    MODIFY S_YMTH.
ENDLOOP.
ENDFORM.                                                    " chg_mtart
*&      Form chg_werks
      text
--> p1        text
<-- p2        text
FORM CHG_WERKS.
CONCATENATE P_WERKS 'Total' INTO WTEXT SEPARATED BY SPACE.
PERFORM PRN_TOT TABLES W_YMTH.
CLEAR: W_DMBTR, W_MENGE, APP.
P_WERKS = I_EKBE-WERKS.
LOOP AT W_YMTH.
    CLEAR: W_YMTH-DMBTR, W_YMTH-MENGE.
    MODIFY W_YMTH.
ENDLOOP.
NEW-PAGE.
ENDFORM.                                                    " chg_werks
*&      Form chg_mth
      text
--> p1        text
<-- p2        text
FORM CHG_MTH.
READ TABLE YMTH WITH KEY YYMM = PMTH.
IF SY-SUBRC EQ 0.
    YMTH-MENGE = W_MENGE.
    YMTH-DMBTR = W_DMBTR.
    MODIFY YMTH INDEX SY-TABIX.
ENDIF.
CLEAR: W_MENGE, W_DMBTR.
PMTH = CMTH.
ENDFORM.                                                    " chg_mth
*&      Form clr_ymth
      text
--> p1        text
<-- p2        text
FORM CLR_YMTH.
LOOP AT YMTH.
    CLEAR: YMTH-DMBTR, YMTH-MENGE.
    MODIFY YMTH.
ENDLOOP.
ENDFORM.                                                    " clr_ymth
*&      Form prn_tot
      text
--> p1        text
<-- p2        text
FORM PRN_TOT TABLES I_YMTH STRUCTURE YMTH.
CLEAR: W_DMBTR, W_MENGE, W_DMBTR1, W_MENGE1, APP, APP1, APP2.
READ TABLE I_YMTH WITH KEY YYMM = LMTH2.
IF SY-SUBRC EQ 0 AND
     I_YMTH-MENGE NE 0.
    W_DMBTR = I_YMTH-DMBTR.
    W_MENGE = I_YMTH-MENGE.
    READ TABLE I_YMTH WITH KEY YYMM = LMTH1.
    IF SY-SUBRC EQ 0.
      APP = W_DMBTR / W_MENGE.
      APP1 = I_YMTH-DMBTR / I_YMTH-MENGE.
      APP2 = ( APP1 - APP ) / APP * 100.
    ENDIF.
ENDIF.
WRITE:/ WTEXT, ' Amount ',
         'USD'.
LOOP AT I_YMTH.
    SELECT SINGLE * FROM TCURR
      WHERE FCURR = 'SGD'
      AND   TCURR = 'USD'.
      I_YMTH-DMBTR = I_YMTH-DMBTR * TCURR-UKURS.
   WRITE AT I_YMTH-COL(12) I_YMTH-DMBTR NO-ZERO.
ENDLOOP.
WRITE:/(18) ' ', ' Quantity'.
LOOP AT I_YMTH.
   WRITE AT I_YMTH-COL(12) I_YMTH-MENGE NO-ZERO.
ENDLOOP.
WRITE:/(18) ' ', ' APP     ', 'USD'.
LOOP AT I_YMTH.
    IF I_YMTH-YYMM NE '999901'.
      CLEAR APP.
      IF I_YMTH-MENGE NE 0.
        APP = I_YMTH-DMBTR / I_YMTH-MENGE.
      ENDIF.
      WRITE AT I_YMTH-COL(12) APP.
    ELSE.
      WRITE AT I_YMTH-COL(12) APP2.
    ENDIF.
ENDLOOP.
ULINE.
CLEAR: W_DMBTR, W_MENGE, APP.
ENDFORM.                    " prn_tot

Adding a new field to existing structure

HI all
I am adding a new field to the existing structure in BW ,shall I remove all the data in the cube to fill fill this field for the previous records and reload again or any other solution
thanks in advance

Hi,
Yu need to delete the data to fill the new field again.
Assign points if it helps
Regards,
Srinivas

Add 2 new fields to an existing ABAP query in a particular position

Hello,
I have added 2 new fields to an existing ABAP query. These have been successfully added and the query is also executing.
But these 2 new fields are displaying at last. I need to add these fields in a particular column position.
Also I need to change the heading of these 2 new fields.
I tried to do so from the basic list, layout design from SQ01.
But I could not.... whatever I do.. the 2 new fields are displayed at the end of the list...
Please help me

Hi Andreas,
Do you mean that I should create a complete new abap query?
Is there no way to add some new fields at a particular position to an existing abap query?

Problem adding a new field to existing BPS planning layout

Hi
I am new to BPS and planning
I have a requirement to add a new field which has values maintained as 0 and 1 to an existing planning cube.The user wants this new field in the existing planning layout where in he can enter the values for this field as 0 or 1.I have created a new field and maintained values for this field as 0 and 1.I have added this field to the existing planning area and have created variable with fixed value with range 0 to1.I have added the same in selections in existing planning level and package as well along with other existing selection conditions.
In additional functions of adhoc package they have made setting as set to all possible char combination.
In this planning area all the selections are locked in planning level and package.
Now when i execute the planning layout to enter data,my new field is grayed out,it does not allow me to enter the values.need help with this as to how can i make this field input enabled.This is an independent characteristic.
Thanks
Panchan

Hi,
Yu need to delete the data to fill the new field again.
Assign points if it helps
Regards,
Srinivas

Adding new field in an existing condition table

Dear friends,
I have an existing condition table for material exclusion with the combination of Plant and material.
Is it possible to change this table and add a field of division also?
Regards,
Ronnie

Hi,
The optimzed solution is to better create a new sequence of fields including the division, so that a new condition table is created based on the key combination or access sequence.
You can add a new field to an existing condition table using APPEND structure facility in Se11. But once on activating the table, how will this division field get populated in the table.
But whereas if you create a new key combination, the data for this condition tables will automatically gets filled up while creating master data thro VK11.
So, its better to go for a new access sequence combination
as a new table is created for this key combinations.
Regards,
JLN

Adding a new field to search of Service Contracts

Hi Experts,
I have a requirement where in to add an existing field i.e your ref (sold_to) your_ref_sold field into the search criteria of Service Contrct .
How to add the field to the Search .
I have few questions here.
1 need I use EEW to add the field to Search but its already existing?
2 If not How to append the Structure crmst_query_src_btil and enhace it with field required?
3 how to implement the BADI crm_rf_search_eew?
Thanking You,
Sree.

The search help exit allows you to modify functionality of search help. If you add a new field to the
parameter list that is not contained on the selection method you can manually populate it within the search
help exit.
This would be performed within the u2018STEP DISPu2019 section. Once within this section all search help
data has been retrieved and is stored in table RECORD_TAB (record_tab-string) as one long string value.
Therefore you need to read table SHLP in-order to locate position of value within string.
Example:
To find position of personnel number (PERNR) within elemenory search
help M_PREMN you would use the following code:
Loop at record_tab.
     read table shlp-fielddescr into wa_shlp
                                   with key tabname   = 'M_PREMN'
                                            fieldname = 'PERNR'.
You could then use this information in the following way, for
example, to find a persons organisation unit:
      select orgeh endda
        up to 1 rows
        from pa0001
        into (ld_orgeh,ld_endda)
       where pernr eq record_tab-string+wa_shlp-offset(8)
                                                  u201Cpernr length is 8
       order by endda descending.
      endselect.
      select single orgtx
        from t527x
        into ld_orgtxt
       where orgeh eq ld_orgeh and
             sprsl eq sy-langu and
           ( endda ge sy-datum and
             begda le sy-datum ).
If you have added a new field to the end of the parameters list
the next step is to populate it by adding this data to the end of
the record_tab string:
concatenate record_tab-string ld_orgtxt into record_tab-string.
modify record_tab.
endloop.

Adding a new field to Emigall

Hi All,
I was interested in knowing how we can add a new field to an existing emigall object and also how to process the logic after adding the field ie. how would emigall handle the field after we have added the field in emigall.
I would appreciate if you can share the screen shots (if any) at karanchopra dot kc at gmail dot com.
Thanks,
Karan

Hello,
Before I provide you with solution, can you be more ellobrative with your requirement.
a) Are you adding new 'Z' field?
b) Do you want to just extend the existing Structure?
Depending on your requirements, there are different approaches to solve this problem.
Regards,
Anup Mohite

BUPT - New field at BUT000 - No BDOC

Hello,
i've added a new field to but000 with an append structure.
The field is shown in a new screen within the genaral data.
This new field was added with the posssibilities in BDT.
When i change the value of the field within transaction bp, the value is written to the database, but there was no BDOC created so that the data is send to the middleware.
The middleware is allready advanced, so that a data exhange between the backend R/3 system and the CRM Sytsem and the CDB is possible.
So what i've to do, that the middleware flow is triggerd when i change the field with transaction bp.
Best regards,
Strehle Thomas

From whatever you have said...where ever you are saving data in BUT000...select corresponding entries from JGTBP00 with BP as key..and them make changes in work area JGTBP00 and modify the data in the database table.

How to add a new field to an existing Generic Search result list?

Good day,
I'm new to the concepts of the Generic Search Framework. I'm attempting to add a new field to an existing result list, and have that new field restricted to a value of "C". This new field will not be displayed, it is only used to ensure that Invoice Documents with a DocStatus of "C" are returned to the B2B Application.
From the *modification\generic-searchbackend-config.xml file, the existing
<h4><property-group name="billing_resultlist_B2B_R3">
<property name="BILLINGDOC" columnTitle="sbt.sbs.genericsearch.billing.invoice.title" parameterType="rowkey" hyperlink="b2b/documentstatusdetailprepare.do" linkParamClass="com.sap.isa.ui.uiclass.genericsearch.GenericSearchUIDynamicContent" linkParamMethod="buildAttributesForBillingDocumentDetails" linkTargetFrameName="form_input" />
<property name="BILL_DATE" type="date" columnTitle="status.sales.date" writeUnderProperty="BILLINGDOC" defaultSortSequence="DESCENDING" />
<property name="NET_VALUE" type="number" columnTitle="status.billing.detail.netvalue" fieldOutputHandlerClass="com.sap.isa.ui.uiclass.genericsearch.GenericSearchUIDynamicContent" fieldOutputHandlerMethod="buildBillingNetValue" cssClassName="amount" />
<property name="CURRENCY" type="hidden" />
<property name="PAYER" columnTitle="gs.hd.gl.partner" linkParamClass="com.sap.isa.ui.uiclass.genericsearch.GenericSearchUIDynamicContent" linkParamMethod="buildShowPartnerLinkSales" />
<property name="PAYERS_GUID" type="hidden" />
<property name="SD_DOC_CAT" type="hidden" />
<property name="OBJECTS_ORIGIN" type="hidden" />
</property-group>
</h4>
I'm trying to better understand how the R/3 tables and columns are specified in the Generic Search Framework. I know that the R/3 table and field is: VBRK.RFBSK, but in the configuration XML files, I never see this exact information specified.   How it is specified to be a part of the result set?
After reading the section in the Development and Extension Guide, I also learned about the "allowedValue" definition, and I believe that I will use that to specify the "C" value for the Invoice Document Status field.
I would greatly appreciate any help.
Thanks,
_kevin

Hi Kevin,
this means you are working in this section of the generic-searchbackend-config.xml
             <property-group name="SearchCriteria_B2B_Billing"
                             useSearchRequestMemory="true">
Below this property
                <property name="IRT_BDH_BILL_TYPE"
                          type="box"
                          entityType="BEART_BILL_TYPE"
                          tokenType="EXP"
                          requestParameterName="rc_documenttypes"
                          label="gs.att.lbl.doc.type"
                          UIJScriptOnChange="GSloadNewPageR3(this);">
                    <allowedValue value="ORDER"           description="b2b.status.shuffler.key1val2"/>
                    <allowedValue value="QUOTATION"       description="b2b.status.shuffler.key1val1" />
                    <allowedValue value="INQUIRY"         description="b2b.status.shuffler.key1val11" />
                    <allowedValue value="ORDERTMP"         description="b2b.status.shuffler.key1val3" />
                    <allowedValue value="CONTRACT"        description="b2b.status.shuffler.key1val4" />
                    <allowedValue value="INVOICE"         description="b2b.status.shuffler.key1val5" default="true"/>
                    <allowedValue value="CREDITMEMO"      description="b2b.status.shuffler.key1val6" />
                    <allowedValue value="DOWNPAYMENT"     description="b2b.status.shuffler.key1val7" />
                    <allowedValue value="AUCTION"         description="b2b.status.shuffler.key1val9" />
                </property>
please try adding this new property
                <property name="DOCUMENT_STATUS(1)"
                          entityType="CL_CRM_REPORT_SET_STATUS"
                          tokenType="RAN"
                          type="hidden"
                          requestParameterName="rc_status_head1" value="C" />
This should do the trick. Unfortunately, I don't have a E-Commerce scenario with an ERP backend for testing purposes available to you have to test it yourself. Keep me updated with the test results !
Philipp Koock
SAP CRM Web Channel Consultant
http://www.koock.net

Error while adding a new field to the Segment in we31

Hi ,
I am getting error when i am trying to add the new field to the cust. segment.
It is released for the adding the new fields i am cancelling the release , but i got a message like this
Error while resetting release of segment 'segment name'.
it is comming from the message class EA and message number 259.
Thanks in advance.
Reagrds,
bharani

Hi,
Have you tried Cancelling the release before adding the version?
Select the active version of the IDOC Segment and cancel its release first. Only then you will be able to add a version.
Please let me know if it worked!
Vijay

Enhancement Adding a new field to a infotype

We are implementing E-Recruiting and trying to a new field to a existing infotype 5107. On the E-Recruiting page there are three frield that already exist. Country, State and City these field also in infotype 5107 too. Country and State both are dropdown box. I have to set the default value for Country to 'USA' and State to 'AZ' where can i set this? The new field will display location "county" which the user will be able to select multiple locations. I know i would have to go PM01 to add the new field to the infotype 5107. But i'm missing the third that will allow me to do this. There's IT, IT Version, IT (i don't have this on my SAP Gui). I'm not sure what to do next after I created this new field. how can put this new field this the E-recruiting webpage?

Matthew,
You can enhance your infotype 5107 from tcode 'PPCI' not 'PM01'.
Check out this Custom Infotype Creation in ORG Management
Regards,
Ahmad

Adding a new field to ODS?

Hi folks,
May i know the procedure as to how to add a new field to already existing ODS?
Thanks in advance
Dubbu

>
Dubbu wrote:
> Thanks alll for your swift replies,
>
> How can i add to the end of the list.?
> Do the infosource and the updates rules gets effected by changing the structure of the ODS. ?
>
> thanks in advance
> dubbu
As Siggi suggested you need to add as last element in the DSO if you have data in DSO.
Just drag and drop your field as the last field.
Do the infosource and the updates rules gets effected by changing the structure of the ODS. ?
Your update rule will go inactive as this new field will need mapping.
You may need to get the vaue for this field from datasource (hence need to manipulate infosource) or you can write routine etc in the udpate rules itself (if thats the req).
All these change attached to transport should go in fine to your production/Test environment.

Adding a new field to a Z table

We have a Z table on which we have created a datasource. We have created a virtual cube on this datasource and queries are built on this cube. This setup is present on Dev, Quality and Prod environment.
Now we have added a new field to the Z table in Dev. We will be creating a new Infoobject for this new field and will be adding it in the Virtual Infoprovider and also in the queries.
1. Do we need to replicate the datasource so that newly added field is visible to the datasource? If no, is there any way?
2. When I have to transport this to Quality and Prod, do I have to capture all the components and objects (Table,Datasoure,Virtual Cube Queries)? If no, what should I capture in the transport request?

Hi,
First, you have to regenerate the datasource in order to add the field:
1) Log on to source system (where Z table is stored) and go to transaction RSA6.
2) Select the root node and click Expand (icon with '+' sign).
3) Search for your datasource (you can use the binoculars icon).
4) Click on Change.
5) Verify that the field appears on the list. Make sure that "Hide field" and "Field only known on client exit" options are not marked for this field.
6) Click on Save.
7) Select "Datasource" -> "Generate" (CTRL+S) menu option.
8) Use RSA3 transaction in order to verify the new field appears on test extractions.
Then, to replicate the datasource in BI:
1) Log on to SAP BI and go to RSA1 transaction.
2) Go to "Modeling" -> "DataSources" section.
3) Search for your datasource and right click on it. Select "Replicate metadata" from context menu.
4) Add the new InfoObject to the VirtualProvider.
5) Update the transformation which joins the DataSource to the VirtualProvider.
As far as transport requests are concerned, even though it requires more work, it is a good practice to group objects in different transport requests according to their type:
In the source System (R3 for instance):
1) One transport request with the table.
2) One transport request with the datasource and its structure.
In BI:
1) One transport order with the datasource replica.
2) One transport order with the new InfoObject(s).
3) One transport order with the modified VirtualProvider.
4) One transport order with the modified transformations from the datasource towards the VirtualProvider.
5) One transport order with the Queries and their elements.
I hope this helps you.
Regards,
Maximiliano

Adding a new field to a standard webdynpro component's layout

Hi all,
I need to add a new field to a standard webdynpro component's( in my case the component is ''/SAPSRM/WDC_UI_SC_DOTC_BD') layout.How do i go about adding a new field to the standard component's lay out?
can anyone help me with the necessary details?
Regards,
Abhinay.

Check if this is useful to you (Login required)
https://websmp105.sap-ag.de/~sapidb/011000358700001969972008E.pdf
Rgds/Kiran

Adding a new field to an existing BDoc.

Similar Messages

Maybe you are looking for