BAPI Enhancement...

Hi all,
I need to enhance this BAPI 'BAPI_BUPA_CREATE_FROM_DATA'.
Currently this BAPI is using the 'BAPIBUS1006_CENTRAL_ORGAN' structure for Organisation details.
But I need to enhance this structure to add 4 more fields.
So,how to enhance this standard BAPI structure as well as this BAPI in order to meet the Requirement?

Refer [this|http://www.sapdb.info/wp-content/uploads/2008/08/introducing-enhancement-framework.pdf]
Regards
Shital

Similar Messages

  • BAPI enhancements Vs BADI

    Hi All,
      Can any one explain me briefely, what is the relation between 'BAPI enhancements' and 'BADI'?
    Thanks
    naveen

    BADI is just an object-oriented version of user-exit. Instead of entering program code into some function module (as in customer-exit), you define some class which has to implement predefined methods and those methods are fired at predefined points just like an old user-exit. Some BADI can have multiple independent implementations which is much better for software deployment as several developers can implement the same BADI independently.

  • Bapi enhancement using user/customer exits

    It is necessary to have access to all calls and purchase orders to be able to maintain the control of the ERS procedure centrally in the TBB system for the functionality u201CBestellselektionu201D [purchase order selection],. Without delay, all necessary purchase order and call data is provided for the table 'ERS'  u201Crealtimeu201D via the interface from SRM. It must be ensured that this table is always filled for SRM scopes synchronous with the SAP standard tables (EKKO, purchase order header data, EKPO purchase order item data, EKAN vendor address, EKPA partner roles etc.). For this purpose, efforts are made to load this table during each creation or change of a purchase order. On the ERP side, the u201EBAPI_PO_CREATE1u201C, which is called by SRM via RFC in the ERP, serves the purpose of creating purchase orders. The BAPI_PO_CHANGE is used for changes in the purchase orders. These BAPIs can be enhanced by the Customer exits EXIT_SAPL2012_003 respective EXIT_SAPL2012_004. With the help of the exits, a function module is called, which then provides the customer-specific fields of the table 'ERS'
    i want to enhance bapi using customer /user exit
    so how shall i proceed with this requirement ??
    how sahll i code the include for this req???
    i m using the functions ::
    1] EXIT_SAPL2012_003
    2] EXIT_SAPL2012_004
    so how can i enhance the bapi using user exits..
    I want to transfer the data from SRM system to TBB system with the customizzed table filled with this data at ERP ie TBB side .. so plz reply how shall i proceed ???

    Thanks Naresh, it helped...
    Can you please help on the below:
    1. For outbound Sales order IDoc- CRMXIF_ORDER_SAVE_M01,need BADIs for modification of the IDoc before it gets generated.
    2. Need program to generate output as outbound IDoc- CRMXIF_ORDER_SAVE_M01  for sales order conformation/acknowledgement.
    3. Need a BADI after the EDI Sales order is saved.
    Thanks in advance
    Vijay

  • BAPI Enhancement for updating database.

    HI,
    My task is to enhance a BAPI structure in SRM, "BAPIBUS1006_CENTRAL_ORGAN",
    where, when I am trying to append structures its telling me that the BAPI structure cant be enhanced. PLease find an alternative route, or else tell me how do I add some fields which are already in the SAP tables, to the BAPI.
    Regards,
    Gautam

    Hi
    <b>Documetation on Enhancement Category</b>
    Enhancement Category Selection
    Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
    You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
    In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
    Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
    Cannot be enhanced
    The structure must not be enhanced.
    Can be enhanced or character type
    All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
    Can be enhanced or character-type or numeric
    The structure and its enhancement must not contain any deep data types (tables, references, strings).
    Can be enhanced in any way
    The structure and its enhancement may contain components whose data type can be of any type.
    Not classified
    This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
    The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
    If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
    If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
    If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the categorycannot be enhanced in any case.
    If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
    If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.
    Regards
    - Atul

  • Fields not getting updated in the database through BAPI enhancement

    Hi Experts,
    I have added 4 custom fields in the transaction FB60. The fields are getting displayed in vendor line item.
    I have to fill these fields from an inbound idoc which uses the BAPI_ACC_DOCUMENT_POST bapi. I have implemented the BADI BADI_ACC_DOCUMENT to pass my custom fields to the bapi and it is processing correctly by adding the custom field values to the extension table that is getting passed to the standard program of the BAPI from the BADI.
    But I think, I have missed to append my fields in one of the standard structures. I have added the fields in BSEG, CI_COBL( which is getting called in BAPICOBL_CI, ACCIT).
    Can anybody tell me which other standard structure I should add my custom fields so that it functions properly and gets added to the BSEG table.
    Regards,
    Sangeeta.

    Solved on own.

  • BAPI Enhancements - Custom Table

    Hi,
    I need to update a Custom Table when i call a Bapi of Change Orders.
    Is it possible use Parameter Extension_In? And how to develop it?

    Ramesh, thanks for your answer.
    I know it is possible write code in a Badi or User Exit, but is it possible manage Custom Table as Append Structure for updating Custom Fields?
    Is it possible use similar code?
    lt_extension_in-structure = 'ZTABLE'.
    lt_extension_in-valuepart1 = zvalue1.

  • How to use Extensionin, Extensionout FOR BAPI ENHANCEMENT

    Hi,
    I need to do the enhancemen for BAPI. I don't know how to do it.
    if there is any good procedure plz give me.
    Thanks in Advance,
    NV

    Hi ,
    In the EXTENSIONIN param Structure should be BAPI_TE_XXXXX(Which has the custom fields) .
    If you don't know one in se11 search with BAPI_TE_* , I am sure you will one which has ur fields.
    And then in Value part1 should have your data.
    For Ex. you want to send company code , asset no.
    first4 will be your comp code , Next 12 will ur Asset no .
    Please revert back if more help required.
    Also Check for similar work
    [Thread|Re: How to use BAPI]
    Rhea.

  • BAPI to add custom fields in delivery BAPI_DELIVERYPROCESSING_EXEC

    Hi Experts,
    We are having zfield in delivery item (appended zfield in LIKP table). Our requirement is to save data of this zfield via BAPI.
    we are using the BAPI BAPI_DELIVERYPROCESSING_EXEC, by passing the zfield to the structure u2018Extension2u2019
    We found while debugging that the data is getting populated in Extension2 but not updated in the table.
    Kindly provide your valuable inputs to update the table.
    Appreciate your <sign of impatience removed by moderator> Response.
    BR
    Sree
    Edited by: Thomas Zloch on Jun 30, 2011 10:08 AM

    Hi
    If the field is non char, perhaps the problem is the format. See Note 509898 - BAPI enhancement concept and Unicode.
    As note says:
    These data structures must only contain character-like data
    Regards
    Eduardo

  • Need enhancement for KS01 Transaction for Department Filed

    Hi Gurus,
    Iam having a requirement on KS01 transaction to find enhancement for Department field.
    Here I could not find any enhancement Exit to proceed further.
    Please let know is there any alternate solution:
    Here is my comlete rquirement below:
    1.Make the u2018Departmentu2019 field, (CSKSZ-ABTEI), mandatory in the Cost Centre Master Record using   screen program name SAPLKMA1 and screen number 0300.
    2.Check the entry made in the u2018Departmentu2019 field, (CSKSZ-ABTEI), in the Cost Centre master record
    When the transaction KS01 is saved check the value in the u2018Departmentu2019 field, (CSKSZ-ABTEI), against values stored in a variable in a Z table by Controlling Area, if matched allow creation, if no match go to the first message below.
    3.Department field is not allowed to be changed once postings have been made to the Cost Centre.
    Check for transaction KS02 or KS12 when save check if u2018Departmentu2019 field has been changed, if no change continue, if changed check to see if postings have been made to the Cost Centre (table COEP), if postings have been made give the second error below, if no postings allow changes to be saved.
    Thanks & Regards
    Bhaskar

    Hi,
        Check following User Exits in SMOD all are for KS01.
      Exit Name           Description
    COCCA001            Customer enhancement to cost center authorization checks
    COCCA002            Customer Functions for Organizational Authorization Checks
    COOMEP01            CO-OM: Information system -> line item reports
    COOMKA01            Customer Fields for Cost Element Master Data
    COOMKS01            Customer Fields for Cost Center Master Data
    COOMKS02            Cost Center: Checks When Saving
    COOMKS03            Cost Center: BAPI Enhancements
    COOMLA01            Customer Fields for Activity Type Master Data
    Salil....

  • Enhancement for ksb5

    HI all,
            I need to do replace fieds for report run trough tcode ksb5.it is an controlling document.
    my requirement is - after the report is displayed we can see unit and quantity fields,those where picked from ekpo table,but i need unit and quantity from esll table.which are enterd in services tab in PO.how to do.please explain me in detais.points are awarded for all helpful replies.thank you

    You could try these enhancements.Reward points if you find it useful.
    Ankur Bhandari
    COCCA001            Customer enhancement to cost center authorization checks
    COCCA002            Customer Functions for Organizational Authorization Check
    COOMEP01            CO-OM: Information system -> line item reports          
    COOMKA01            Customer Fields for Cost Element Master Data            
    COOMKS01            Customer Fields for Cost Center Master Data             
    COOMKS02            Cost Center: Checks When Saving                         
    COOMKS03            Cost Center: BAPI Enhancements                          
    COOMLA01            Customer Fields for Activity Type Master Data           
    KMA10001            Customer Fields for Activity Type Master Data

  • Error 70  - Código do status 225: Rejeição: Falha no Schema XML da Nfe.

    Bom dia grupo!
    Nós estamos atualmente recebendo a seguinte mensagem de erro da SEFAZ relacionado aos batches que nós enviamos: Error status 70 "Error from the authorities" and Código do status (Status Code) 225: Rejeição: Falha no Schema XML da Nfe.
    Nossa configuração é 46C com muitos OSS notes aplicados (veja abaixo)
    Nós estamos realmente parados neste momento e não temos nem ideia de onde começar.
    Atenciosamente,
    Marc de Ruijter
    OSS notes for NF-e phase 2
    989115      Nota Fiscal Electronica (NF-e) - Overview Note
    852302      Implementation Overview ISS 2004 - Legal Change MP135/LC116
    759965      New Condition Formulas for MP-135 and ISS 2004
    747607      Basic Customizing for MP135 and ISS legal change Brazil
    980214      DDIC changes: PIS / Cofins Tax Law and Tax Situation
    981123      PIS / Cofins Tax Law and Tax Situation
    981687      NFe: For Services in Muncipio Sao Paulo
    934846      Syntax error: TYPE-POOL 'SXRT' is unknown
    979881      Message S 000 in NF writer when mandatory fields not filled
    980213      Nota Fiscal Electronica (NF-e) of SEFAZ - Phase 2
    1037070      NF-e of SEFAZ - Phase 2, Enhancement 01
    1014600      No output found for the Nota Fiscal
    1052575      NF-e of SEFAZ - Phase 2 / DDIC changes after shipment
    1043688      NF-e of SEFAZ - Phase 2, Enhancement 02
    1062468      NF-e: Multiple volume structure for XML file
    1062251      NF-e: Extension of BADI Interface FILL_HAEDER
    1070261      NF-e of SEFAZ - Phase 2, Enhancement 03
    1094041      NF-e of SEFAZ - Phase 2, Enhancement 04
    1000130      Public System for Digital Bookkeeping (SPED) - Overview Note
    1008306      SD: Manual changes of CFOP for services when ISS tax applies
    998194      Missing ISS Tax Situation in the Nota Fiscal
    1047606      SD/Brazil: Using of error log during Nota Fiscal creation
    120449      SD-Brazil Exchange variance error in Nota Fiscal
    92383      LSA:BR:SD: Tax laws in return nota fiscal
    689157      Nota Fiscal Split and number of Packages
    987882      ISS Tax Law (field J_1BTAXLW3) not copied from sales order
    989965      CFOP redermination in the delivery document not working
    909835      Message 8B 679 raised during the delivery process
    337554      SD: No. of packages in Nota Fiscal
    533046      Repair order inconsistent to object list
    920330      Error when changing the tax codes in a sales order
    998195      PIS/COFINS/ISS Tax Law and Tax Situation in SD
    104606      EDI/IDoc: Mapping IDoc types to ANSI X12
    1094041      NF-e of SEFAZ - Phase 2, Enhancement 04
    1105588      J_1BLFZF: Runtime error OBJECTS_OBJREF_NOT_ASSIGNED
         OSS notes for XML ver 1.1 and NF-e phase 3
    1065334      NF-e: Extension of BADI Interface FILL_ITEM with tax table
    1068615      NF-e: Extension of BADI Interface with SD document flow
    1079826      NF-e: BAdI Interface Enhancement for NF Messages
    1069919      NF-e: Partner in Block E should always be main partner
    1090279      NF-e monitor: automatic refresh upon user actions
    1093252      NF-e: ICMS tax situation in XML File and DANFE
    1113127      NFe: New XML Layout - Version 1.10
    1114348      NF-e - xNFe integration - backend
    1122294      Send/resend NF-e: fill VBFA for BAdI item method
    1124075      NF-e: Serie not taken from Contingency NF-Type
    1144194      NF-e: Cancellation/Skipping Reason
         Bug Fix notes for NF-e BAPI.
    1049946      NF-e: Adaption of Nota Fiscal Bapis
    1147934      NFe: Random number should not be generated for incoming NFes
    1150733      NFe: Randon number and check digit not cleared
    1154995      NF-e: NF BAPI - enhancement for NF-e processing
    1158622      NF-e: NF BAPI - no input of random number possible
         Bug Fix notes for Contingency process
    1158612      NF-e: Wrong partner in Block-E for Entrada
    1240212      NF-e: One time Vendor data not transferred to XML file
    1255450      NF-e: Jurisdiction code for one time vendor / customer
    1257030      NF-e: Country Name for one time vendor / customer
    1069018      Cancellation of incoming NFe shows error J1B_NFE 003
    1070077      NF-e: Protocol number and document status for Denied NF-e
    1145148      NFe: Cancellation for Contingency NFes
    1152263      NF-e monitor: wrong action status '7' for C-NF-e
    1146914      NFe: Synchronous call to messaging system from backend
    1149356      NFe: Dump when NFe is cancelled with MIGO
    1152081      NFe: Dump when NFe is cancelled with VL09
    1153533      NFe: Dump when NFe in contingency is cancelled with VL09
    1156116      NF-e: Contingency by stock transfers
    1160107      NF-e: Cancellation of contingency NF-e with DOCSTA = 1 or 2
    1161347      NF-e: Cancellation of Contingency NF-e - correction
    1238648      NF-e monitor: req. action '3' (send) wrong for swtch. NF-e
    1165953      NF-e: Numbering Gaps
    1244326      NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP
    1245425      NF-e monitor: required process step - contingency
    1252567      NF-e: Resend of NF-e - rejected or with validation error
    1266344      NF-e: Action Indicator for NF-e with validation error
    1254565      NF-e: Synchronization of RFC call between ERP and xNFe
    1053626      MIRO: wrong document reference in nota fiscal
    1073259      NF-e: Transfers - Outgoing NF-e No. not taken by Incoming
    1153874      NF-e: GR for future delivery takes wrong NF-e number
    1174946      NF-e: Serie not considered for duplicate NF-e number in MIRO
         Miscellaneous bug fix notes
    1175538      NF-e: Reference between NF and NF-e
    1244881      NF-e: Mixed scenario in MIRO shows error 8B219
    1257422      MIRO: Error 8B 219 by posting of reference invoices
    1150843      NFe: Text for cancel reason not transferred to XML file
         Bug Fix Notes Group 2
    1059699      NF-e: Reference between NF and NF-e
    1139062      NF-e incoming: Posted via J1B1N -> Wrong Document Status
    1144199      NF-e: SD Billing and Contingency
    1145089      NF-e: Cancellation despite rejected cancel request
    1149787      NF-e: Wrong status-code text in NF-e history
    1151112      NF-e: cancellation-reason text gets lost (pre req of 1150172)
    1150172      NF-e monitor: selection leads to dump
    1068379      Creation of Billing document issues an error 8B 145 (pre req of 1145089)
    1152842      NF-e: cancellation reason does not work
    1154700      NF-e: Random number & check digit not stored in active table
    1073145      PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
    1082527      Missing PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
    997868      VL02N: CFOP, tax laws not copied from delivery (error 8B148) u2013 (pre req of 1155231)
    1155231      PIS/COFINS tax law in NF/NF-e by split valuated material
    1155424      NF-e monitor: Menu -> "Check MS Connection" does not work
    1159177      NF-e: FUNC J_1B_NFE_SET_STATUS_IN_BACKEND set as Rem.Enabl
    1161951      NF-e monitor: "Resend" functionality.
    1162232      NF-e: switch to contingency not possible after MSS Update
    1162512      NF-e: cancellation reason not initial at first-time call.
    1162629      NF-e: creation date gets deleted from NF-e data-base table
    1164283      NF-e: SCS '5' - upon authr.to cancel system does not cancel
    1165155      NF-e Monitor: BACK (F3) leads to cancellation
    1165360      NF-e Monitor: new selection parameter - creation user
    1168394      NF-e: Reference document not taken from Nota Fiscal header
    1168798      NF-e: User decision for used NF-Type for Material Movements
    1171383      NF Writer: Copy NF-e that was switched to contingency.
    799445      Nota Fiscal creation: Consideration of local dates (pre req of 1171383)
    1104003      NF-Writer: Serie not taken from Reference NF (pre req of 1171383)
    1156037      NF-e: NF-Writer allow reference with different NF-types (pre req of 1171383)
    1175759      NF-e: central contingency per business place - correction
    1239598      NF-e: Random number and check digits are lost in NF writer.
    1163888      NF-e: Random Number includes spaces (pre req of 1239598)
    1245425      NF-e monitor: required process step u2013 contingency. u2013 applied in bug fix notes no need to apply.
    1246700      NF-e: Wrong reference for NF entradas.
    1257688      NF-e: Update termination with error J1B_NFE 021
    1258021      NF-e: Dump by creation of NF header text for XML file
    1258974      NF-e: Monitor report aborts with DBIF_RSQL_INVALID_RSQL
    1265172      NF-e - Decouple RFC from DB Update
    1285851      NF-e: Cancellation of none authorized documents
    1288925      NF-e: References between NF-e and non NF-e
    1272677      NF-e: Cancellation for Material Document with serial number (pre req for 1288925)
    1247602      NF-e: Cancellation of material documents with serial numbers
    1163104      NF-e: Cancel Material documents with initial cancel reason
    1293944      NF-e: Cancellation of material documents with batch classes.
    1267128      NF-e: Cancellation goods movement with MVT 844 not possible (pre req for 1293944)
    1300000      NF-e: Decouple - Contingency
    1314856      NF-e: Decouple - Contingency in J1BNFE and VF01 & VF04
    1321837      F-e: Cancel of material documents not possible
    1092028      NF-e: Protocol number in NF-header overwritten (pre req for 1265172)
    1114283      NF-e: cancellation - document status cleared in J_1BNFDOC (pre req for 1265172)
    1234053      Local time / local date in NF header and NF-e XML (pre req for 1265172)
    1288994      NF-e: Decupling note 1265172 causes error for incoming NF-e (pre req for 1300000)
    1297042      NF-e: NF-e number missed in access key after decoupling (pre req for 1300000)
    1087535      RFFOBR_A,U:Doc.no should be filled with 9 digits in DME file Applied OSS note 1087535 to the object Z_RFFORIY1 which was copied from RFFORIY1
    1097455      NFE: Bank files should accommodate Doc. Numbers with 9 digits
    304961      Wrong boleto check digit with carteira data (pre req of 1097455) - Not relevant
    336117      Include due date factor in Boleto barcode for A/R (pre req of 1097455) - Not relevant
    705726       ITAU: Boleto has negative interest value (pre req of 1097455) - Not relevant
    846297      Func Mod - BOLETO_DATA not printing correct nosso numero (pre req of 1097455) - Not relevant
    852782       BOLETO_DATA - Corrections of note 846297 for Bredesco only (pre req of 1097455) - Not relevant
    1227478      Dump in payment run (F110) when XBLNR is empty
    1138278      NFe: Field PREDBC not filled in XML interface structure (pre req of 1149585)
    1149585       NFe: CST field required in XML file for taxes not in NFe
    1053855      VL02N raises error 8B 053 "Branch not foundu201D
    1165696      RFEBBU00: Error in batch input due to changes in Nota Fiscal
    1180402      NF-e: BADI methods FILL_HEADER and FILL_ITEM
    1180672      NF-e: Gap numbering check doesnu2019t consider the series
    1225338      RFEBBU00: Additional changes to the note 1165696
    1241922      NF-e: Report J_1BNFECHECKNUMBERRANGES xNFe adaption
    1244326      NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP (Applied using other Kintana)
    1270813      NF-e: Year not included in the XML file
    1247264      NF-e: Error in RFC to /XNFE/NFE_CREATE after note 1241922 (pre req for 1274200)
    1274200      NF-e: Numbering gaps report sends SERIE with spaces
    1276185      NF-e: Numbering gaps report sends SERIE with spaces
    1294917      NF-e: Gap numbering check - several corrections
    1324538      Missing address for OT Customer in J_1B_NFE_CREATE_TXT_FILE
    1331432      NF-e: Numbering gaps report detects gaps for initial series
    1332167      NF-e: Rep. J_1BNFECHECKNUMBERRANGES aborts with error DC 006
    1092341      RFFOBR_A,RFFOBR_D: Performance problem while rebate calcula
    1237089      RFEBBU10:While uploading ITAU Bank returnfile- Error(F5 170)
    1051314      Check Digit missing from Boleto number (pre req for 1306966)
    1306966      J_1BBR30:XREF3 is not updated correctly with Boletofrom bank
    1005924      RFFOBR_A-The DME file does not include Rebate for ITAU (pre req for 1287633)
    1287633      RFFOBR_A: Discount amount not calculated correctly
    1234054      NF-e: function J_1B_NFE_MS_REQUESTS_DATA is not RFC enabled
    1297534      NFe cancellation problems in GRC
    1243964      NF-e: Adaption of xNFe interface of function NFE/NFE_SKIP
    1165746      NF-e: Cancel - Error log not updated
    1327465      The program /xnfe/update_erp_status is not updating R/3
    1326691      BAdI for controlling the RFC call of external systems
    1333136      Prevent simultaneous click on buttons in NF-e monitor
    1333742      NF-e got the status 218
    1354192      Validation rules: correction for fields TPLACA and T_UF1
    1373175      Lock object for /XNFE/NFE_CREATE to prevent double transm
    1376500      BAPIRET2 to provide the detailed information to ERP
    1267455      Not possible to create different DOCREF per item using BAPI (pre req for 1373321)
    1373321      BAPI_J_1B_NF_CREATEFROMDATA: DOCREF from Header go to item
    1328583      NF-Writer posting of NF/NFe when mandatory fields not filled
    1338166      NF-e: Random number and check digit lost after note 1328583
    1259918      NF-e: RFC calls for request for cancellation or skip
    1152140      NF-e: backend allows inconsistent new SCS (pre-req for 1298283)
    1162852      NF-e: Inbound errors missed in error log of Monitor Report (pre-req for 1298283)
    1163056      NF-e: Problems with printing via BADI method CALL_RSNAST00 (pre-req for 1298283)
    1276438      NF-e: Parallel Phase not identified in messaging system (pre-req for 1298283)
    1296515      NF-e: J1BNFE reset rejected NF-e after skipping request (pre-req for 1298283)
    1297823      NF-e: Cancelled NF-e shows wrong action indicator (pre-req for 1298283)
    1298283      NF-e: Skip for NF-e with validation error
    1362969      NF-e: check cancellation for billing documents
    1368159      NF-e: cancellation of invoices via original application only
    1370933      NF-e: Accept Rejection to Cancel - wrong status in monitor
    1376324      NF-e: Skip for NF-e with validation error
    1140579      NFe: Field length conflicts from backend interface to XML
    1357713      NF-e: Cancel of incoming NF-es does not update active table.
    1173018      NF-e: Field control for Random Number and Check Digit (pre-req for 1366320)
    1321517      NF-e: MIRO Credit Memos for NF-e shows error 8B 020 (pre-req for 1366320)
    1366320      NF-e MIRO:Save is allowed without mandatory fields filled for NFe
    1375066      NF-e: J_1BNFECHECKNUMBERRANGES ends too early, wrong subrc
    1375894      NF-e: J1BNFE authority check for company code
    1377879      NF-e: Report J_BNFECALLRFC aborts with message A098
    1379062      NF-e: posting GR after cancellation leads to wrong NF-e
    1357777      Cancel billing document without Nota Fiscal cancellation
    1380861      NF-e Resend(proc.stat.07) with Signature error impossible
    1362025      Error while sending Bacen Code EX with 0 on begining
    1249819      NF-e: Field MODFRETE filled incorrectly

    Bom dia Marc de Ruijter,
    Não dá para ler sua thread, mas imagino que seu validador esteja desligado.
    No GRC vá em SPRO --> SAP GRC Nota Fiscal Electronica --> Configure System Response for Each Tax Number (CNPJ)
    Para ligar/desligar o Validador basta clicar no check box na coluna Validation.
    Observação: Para correto funcionamento do GRC deve-se sempre utilizar o validador ligado.
    Após isto refaça seu teste, é provável que você receba um erro de validação para a NF-e. Veja em GRC Web monitor -> NFe Detailed View -> Validation History.
    Atenciosamente,
    Fernando Da Ró

  • Delivery schedule in purchase requisition should be copied to RFQ

    Hi
    I had a requirement to maintain delivery schedule in purchase requisition which should be copied to RFQ.
    Since standard SAP is not supporting this feature, we maintained delivery schedule for each line item of PR in a custom screen/development.
    Now iam not able to call the same data to RFQ screen through a BAPI / Enhancement.
    Appreciate your valuable comments on above issue.
    Thanks
    Deepak

    Not sure what you expect from us functionals here in MM.
    You have built a function yourself that is not available in standard , and now you expect that other transactions are just taking this into consideration?  Of course you need to modify the entire process chain if you create new functionality which is not foreseen by SAP's standard.

  • PO Custom Field not getting filled from Shopping Cart

    Hi Gurus,
    I am new to SRM. The requirement I had was to add a new field to the SC. I read several posts and articles on this but couldn't find the solution to it. I managed to do this modifying the corresponding structures in SRM and making the necessary changes in R/3 so the new filed can be seen in ME21/22/23N.
    I checked Andreas Milbredt document to achieve it as mentioned:
    Document: How to transfer custom fields from SRM to Backend.
    http://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/20b36c12-685f-2c10-4fb4-ba2e0b969c27
    After that, when I create a Shopping Cart, the value in the New field is not transferred to the Back end.
    I coded the following BADIs and User Exits:
    In SRM:
    BBP_CUF_BADI_2 (MODIFY_SCREEN) ->To enable or disable the field depending on conditions. Works fine.
    BBP_DOC_CHECK_BADI (BBP_DOC_CHECK) -> To do some checks. Works Fine
    BBP_CREATE_BE_PO_NEW (FILL_PO_INTERFACE1) ->Here I fill structures BAPI_TE_MEPOITEM and BAPI_TE_MEPOITEMX. I added another u2018Xu2019 to indicate the new field to BAPI_TE_MEPOITEMX. But I think I am not doing it right. This structure BAPI_TE_MEPOITEM/X, does the order of the fields correspond to the order of the fields in any of these 3 structures (which I am using)?
    INCL_EEW_PD_HISTORY_CSF
    INCL_EEW_PD_ITEM_CSF
    INCL_EEW_PD_ITEM_CSF_SC
    I also checked the following link:
    Map a custom SRM field to a standard field in R/3
    In R/3 I populated the Exits Andreau2019s mentions on his article. Am I missing anything else?
    Thanks & Regards,
    Ernesto.

    Hi Ernesto,
    You can find out how your BAPI structure is being populated (by generating the test data ) using FBGENDAT program and activating the BAPI_PO_CREATE1 (and you will need to set the parameter for the specified user id)... This will provide you ability to execute the BAPI offline and figure out what is happening...
    Note 517767 - Generate test data for function modules
    Things to look for, Is any of your custom fields quantity fields or integer?
    Check out the following OSS note
    Note 509898 - BAPI enhancement concept and Unicode
    Also check out the following SDN Thread,
    problem using  BAPI_BUS2001_CREATE to create project definition
    Check out a similar thread that we are discussing (for PR)
    Custom Fileds Data Was Not Getting Updated In BAPI_PR_CREATE

  • KSB1 user exit & extra column.

    Hi
    How do I add my own extra column on the report "Display actual cost line items for cost centers' - SAP transaction KSB1.
    Thanks
    Rendani

    Hi,
    Pls find the user exits available for the tcode :KSB1 below:
    COCCA001  Customer enhancement to cost center authorization checks
    COCCA002  Customer Functions for Organizational Authorization Checks
    COOMEP01  CO-OM: Information system -> line item reports
    COOMKA01  Customer Fields for Cost Element Master Data
    COOMKS01  Customer Fields for Cost Center Master Data
    COOMKS02  Cost Center: Checks When Saving
    COOMKS03  Cost Center: BAPI Enhancements
    COOMLA01  Customer Fields for Activity Type Master Data.
    Pls reward if helpfull.
    Regards,
    Sharath

  • Field Tax Number 1 in VA01

    Hi I am using the BAPI sd_salesdocument_create to create sales orders and need to pass the field Tax Number 1 (STCD1) for the case of a customer CPD. I'm using the table EXTENSIONIN as follows but not recorded the field.
    EXTENSIONIN-STRUCTURE = 'VBPA3KOM'
    EXTENSIONIN-VALUEPART1 = '          00000010406707933'
    Thanks.

    hi dvalesp,
    Have you tried placing a breakpoint in SD_SALESDOCUMENT_CREATE at SE37?
    perform ms_move_extensionin tables extensionin
                                         sales_items_in
                                         sales_schedules_in
                                  using
                                         sales_header_in.
    This is in line 222-226 of the source code of the BAPI.
    Then check subroutine ms_move_extensionin of include program LVBAKF0C.
    * BAPI enhancement <b>for</b> CPD Customer Information <b>for</b> table VBPA3
          WHEN 'VBPA3KOM'.
            CATCH SYSTEM-EXCEPTIONS conversion_errors  = 1.
              MOVE extensionin+lv_length TO wa_vbpa3kom.
              APPEND wa_vbpa3kom TO ex_vbpa3kom.
            ENDCATCH.
        ENDCASE.
      ENDLOOP.
    try to check what is being transferred in the code "MOVE extensionin+lv_length TO wa_vbpa3kom." You may try to change the value of wa_vbpa3kom during debugging and continue the program to check if it works. If it works, that means all you have to change is the values inside extensionin.
    Regards,
    Paul

Maybe you are looking for

  • Bluetooth not working correctly after iOS 4 update

    I recently purchased and have been enjoying the Bose sound link wireless music system in fact I can't say enough about the accessory connecting wirelessly my iPad and iPhone to enjoy music. After the iOS 4 update my iPhone will no longer connect to t

  • Auto transport of XI objects through CMS

    Hi Gurus, We have XI landscape alongwith JDI configured on Development system.  Currently we are moving XI objects manually through CMS.  Is there any way to move objects automatically through CMS (As we have in ABAP through STMS), if so please let m

  • PCI6602

    Helo, plz help me in installing counterpallets for PCI 6602..I was working in LV 6.1..somehow some programs are opened in LV 7.0 and after that i couldn't drag DIO pallets displaying the error "version 7.0 is newer than 6.2.".how i can I get out of t

  • Acrobat Pro and other CS4 tools won't run.

    Suddenly I can't execute two CS4 tools.  Acrobat Pro reports a CS4 licensing issue and requests that I exceute another product like PhotoShop.  Both versions of PhotoShop report error 148:3. Please advise/help. Joe

  • Huge DVD-9 project needs two Dual Layer discs - How to build a from single project?

    Hello Encore Pros, I have a DVD project with about 5 hours of video media and it won't fit on a single DVD-9.  It has to be built onto TWO Dual Layer DVDs.   I've created the project as ONE BIG PROJECT in Encore CS6 (Mac Pro 10.7.5) with lots of menu