Adição de Campo no App de Preços

Prévia do material em texto

<p>Declaration:</p><p>This is not an official documentation.</p><p>The best way to asking a new field in this ‘Manage Price - Sales’ app is to raise new requirement via</p><p>official channel: Homepage - Customer Influence (sap.com)</p><p>Prerequisites:</p><p>• You are OP system higher than OP1909</p><p>• You have the Dev authorization to do the extension</p><p>• You have value help CDS view(e.g. I_SalesOrganizationValueHelp) for new field(optional)</p><p>• You checked the SAP Help document(e.g. OP2020 Latest) that SAP field not supported in Price</p><p>API</p><p>• You want to add this SAP field and make it available in ‘Manage Price’ Fiori App and OData</p><p>(If you want to add custom field, please use ‘Custom Filed’ App!)</p><p>• In later release, If SAP delivery the same field, you have to remove this field from below</p><p>extensions(Not harmful, as the condition table is reusable). Otherwise you will got dump as</p><p>duplicate field</p><p>• The way of extension only works for ‘Manage Prices’ Fiori App and OData</p><p>In below example, I would like to enable PRODH1. It has VH help and Text.</p><p>Enable SAP fields in F4111</p><p>1. In ADT(ABAP Development Tools) to create extend view for CDS I_SlsPrcgCndnRecdValidity. E.g:</p><p>@AbapCatalog.sqlViewAppendName: 'ZZISLSPRCGCNDNVA'</p><p>extend view I_SlsPrcgCndnRecdValidity with ZZI_SLSPRCGCNDNRECDVALIDITY {</p><p>cast( '' as prodh1 ) as PRODH1</p><p>}</p><p>2. In ADT to create extend view for CDS I_SlsPricingConditionRecordTP. E.g:</p><p>@AbapCatalog.sqlViewAppendName: 'ZIEXVALITP'</p><p>extend view I_SlsPricingConditionRecordTP with ZZI_SLSPRCGCNDNRECDVALIDITYTP {</p><p>@ObjectModel.readOnly: 'EXTERNAL_CALCULATION'</p><p>PRODH1,</p><p>cast( '' as vtext ) as ProductHierarchyNode1Text</p><p>};</p><p>3. In ADT to create extend view for CDS C_SlsPricingConditionRecordTP. E.g:</p><p>@AbapCatalog.sqlViewAppendName: 'ZCEXVALITP'</p><p>extend view C_SlsPricingConditionRecordTP with ZZC_SLSPRCGCNDNRECDVALIDITYTP {</p><p>@ObjectModel.readOnly: 'EXTERNAL_CALCULATION'</p><p>@ObjectModel.text.element: ['ProductHierarchyNode1Text']</p><p>PRODH1,</p><p>@Semantics.text: true</p><p>https://influence.sap.com/sap/ino/#/</p><p>https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/19d48293097f4a2589433856b034dfa5/c8fef622eed042fba2d0ddb749bac7ac.html?version=2020.latest</p><p>ProductHierarchyNode1Text</p><p>};</p><p>4. In case you want value help annotation or overwrite the annotation from standard, In ADT to</p><p>create metadata extensions for CDS C_SlsPricingConditionRecordTP. E.g:</p><p>@Metadata.layer: #CUSTOMER</p><p>@EndUserText.label : 'Condition Record for Pricing in Sales'</p><p>@UI: { headerInfo: { typeName: 'Manage Prices - Sales', typeNamePlural: 'Manage Prices - Sales' }</p><p>}</p><p>annotate view C_SlsPricingConditionRecordTP with {</p><p>@UI.lineItem: [{ position: 201 }]</p><p>@EndUserText.label: 'Product Hierarchy Note1'</p><p>@EndUserText.quickInfo: 'Product Hierarchy Note1'</p><p>@Consumption.valueHelpDefinition: [{entity: {name: 'ZI_ProductHierarchyNode1', element:</p><p>'ProductHierarchyNode'}}]</p><p>@UI.textArrangement: #TEXT_FIRST</p><p>PRODH1;</p><p>@Consumption.filter.hidden: true</p><p>ProductHierarchyNode1Text;</p><p>}</p><p>For UI.LineItem.position better start higher than 200.</p><p>5. In ADT to create extend view for CDS A_SlsPrcgCndnRecdValidity. E.g:</p><p>@AbapCatalog.sqlViewAppendName: 'ZZASLSPRCGCNDNVA'</p><p>extend view A_SlsPrcgCndnRecdValidity with ZZA_SlsPrcgCndnRecdValidity {</p><p>PRODH1</p><p>}</p><p>6. In ADT to create extend view for CDS I_SlsPrcgCndnRecdTemplate. E.g:</p><p>@AbapCatalog.sqlViewAppendName: 'ZIEXTEMP'</p><p>extend view I_SlsPrcgCndnRecdTemplate with ZIEX_TEMPLATE {</p><p>@Consumption.valueHelpDefinition: [{entity: {name: 'ZI_ProductHierarchyNode1', element:</p><p>'ProductHierarchyNode'}}]</p><p>@ObjectModel.text.element: ['ProductHierarchyNode1Text']</p><p>cast('' as prodh1) as PRODH1,</p><p>cast( '' as vtext ) as ProductHierarchyNode1Text</p><p>}</p><p>7. SE11->database table: SDPRCG_CNDNR_D->Add 'Append Structure' with you wanted field,</p><p>Active and you will see below:</p><p>8. SE11->structure: ISSLSPRICINGCONDITIONRECORDT_D->Add 'Append Structure' with you</p><p>wanted field. Active and you will see below:</p><p>9. SE11->structure: ISSLSPRICINGCONDITIONRECORD_DR->Add 'Append Structure' with you</p><p>wanted field. Active and you will see below:</p><p>10. Check the ABAP field name of field control field in SEGW</p><p>11. SE11->structure: SDPRCOMHEAD_INCL_EEW_TR(KOMK) or</p><p>SDPRCOMITEM_INCL_EEW_TR(KOMP)->Add above ABAP Field name into in a 'Append</p><p>Structure', component type CFD_CUSTOM_UI_FIELD_CONTROL, e.g F_PRODH1. Active and you</p><p>will see below:</p><p>12. Add field catalog if not existing, create the new condition table, maintain the access sequence</p><p>and condition type.</p><p>13. If you have business case that send out condition using DRF, you have enhance the SOAP service</p><p>(service name: CO_SDCM_ESR_SALES_PRICING_COND validity structure:</p><p>SDCM_ESR_SALES_PRICING_CONDITI)as well, otherwise custom field will appear in SOAP</p><p>payload. (Current not support, as we can not use MOVE-CORRESONPIDNG)</p><p>Enable Value Help for above new added fields(optional)</p><p>(Detail explain please see this blog)</p><p>1. Create a new SEGW project (e.g. ZSD_PRICING_CONDITIONRECORD) and assign a transportable</p><p>package.</p><p>2. In ‘Data Model’ node to redefine a source OData project</p><p>3. Choose the SAP standard service name ‘SD_PRICING_CONDITIONRECORD_SRV’, Version 0001</p><p>https://community.sap.com/t5/technology-blogs-by-sap/how-to-redefine-rds-based-odata-services/ba-p/13527155</p><p>4. Choose all entities from source OData project</p><p>5. Add your VH help CDS view to this Refined Project</p><p>6. Generate the runtime object for this redefined project</p><p>7. Mark the Service Extension/Extended Service and click Finish</p><p>8. In tx /n/IWBEP/REG_SERVICE, you will see</p><p>9. Copy program from Github zaf_r_extend_rds_based_service.prog.abap</p><p>10. Run this program</p><p>https://github.com/SAP-samples/abap-platform-code-samples-standard/blob/main/TEST_ONPREM_EXTEND_RDS_SRV/src/zaf_r_extend_rds_based_service.prog.abap</p><p>11. You will got the MPC_EXT and DPC_EXT class source code for your EXT_PROJ.</p><p>Copy and activate the code to corresponding MPC_EXT and DPC_EXT class in service project</p><p>ZSD_PRICING_CONDITIONRECORD.(Note: if encounter this error ‘A method implementation</p><p>cannot uniquely be determined’, to correct the method name and some variables with unique</p><p>one)</p><p>12. the service assignment in tx /IWBEP/REG_VOCAN, add a new assignment for annotation model</p><p>SD_PRICING_CONDITIONREC_ANNO_MDL.(SAP Note 3091281 explained if not)</p><p>https://launchpad.support.sap.com/#/notes/3091281</p><p>13. After above assignment, one table entry in DB /IWFND/I_MED_VAA</p><p>14. Now, ‘Manage Price in Sales’(F4111) working with your added SAP field, and it has relevant</p><p>Value Help and description</p><p>Relevant SAP Notes</p><p>• 3050095 - Manage Price - Sales app: Cannot download data for custom fields via View Import</p><p>History</p><p>• 3083180 - Can not maintain non-key fields in 'Manage Price - Sales' App</p><p>• 2520936 - Undo Redefining OData Service</p><p>https://launchpad.support.sap.com/#/notes/3050095</p><p>https://launchpad.support.sap.com/#/notes/3083180</p><p>https://launchpad.support.sap.com/#/notes/2520936</p>