Badl BBP_TARGET_OBJECTS

I've a problem. I need to have, in this badl, the vendor code of the item.
unfortunately the table IT_CUST_ITEM is empty. I found a note of this argument, but not solves the problem.
Have you any ideas?
Thanks Bitta

Hi Bitta,
the table IT_CUF_ITEM contains the customer fields if you have defined some.
Have you tries to run function module BBP_PD_SC_GETDETAIL to get the vendor code?
Regards Olaf

Similar Messages

Change the backend doc type from PR to PO in BADI BBP_TARGET_OBJECTS.

Hi,
We have followed below approach for backend document type determination.
1. A custom function module contains the logic to determine the backend document type of a Shopping cart line item. THis function module, performs many checks and hence cannot be called in any BADI that is executed in Foreground.
2. I am using BADI BBP_TARGET_OBJECTS to change the follow document type by calling the custom function module.
Issue here is, if the backend document type of a line item is Purchase requisition (2) by SAP standard, and if I try to change it to Purchase order, it gives run time error and ends up in creation of Purchase order.
After further investigation I found that this line item (with default backend doc type as 2) has a desired vendor. If we change the desired vendor of this line item to fixed(To Partner function 19 from partner function 39), it allows us to change the doc type from Purchase requisition to purcahse order in BADI BBP_TARGET_OBJECTS.
But changing the partner function is possible only in BBP_DOC_CHANGE BADI, and I cannot call the custom function module there, as it may impact the performance.
Is there any other way, I can change the partner function in any of the BADIs called in background?
Or Is there any way by which I can change the backend document type from PR to PO in BBP_TARGET_OBJECTS?

Hi Parab
if you swaping 39 to 19 viadoc change badi
REQUESTER has a control on Purchase ORDER Vendor and BUYER lost a control so your business has to decide.In this case procurement department lost their control.
Fixed vendors are like inforecord and contract negotiated for best price ..
Muthu

BTE and BAdl

Hi All,
i am new to abap programming.. I work in SAP XI.. can any know provide documentation about BTE and BAdl..

Hi
for BTE
see the link
http://help.sap.com/saphelp_erp2004/helpdata/en/ee/e87988027a11d5a7d60000e83dda02/content.htm
BADI
DEFINING THE BADI
1) execute Tcode SE18.
2) Specify a definition Name : ZBADI_SPFLI
3) Press create
4) Choose the attribute tab. Specify short desc for badi.. and specify the type :
multiple use.
5) Choose the interface tab
6) Specify interface name: ZIF_EX_BADI_SPFLI and save.
7) Dbl clk on interface name to start class builder . specify a method name (name,
level, desc).
Method level desc
Linese;ection instance methos some desc
8) place the cursor on the method name desc its parameters to define the interface.
Parameter type refe field desc
I_carrid import spfli-carrid some
I_connid import spefi-connid some
9) save , check and activateadapter class proposed by system is
ZCL_IM_IM_LINESEL is genereated.
IMPLEMENTATION OF BADI DEFINITION
1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.
2) Specify aname for implementation ZIM_LINESEL
3) Specify short desc.
4) Choose interface tab. System proposes a name fo the implementation class.
ZCL_IM_IMLINESEL which is already generarted.
5) Specify short desc for method
6) Dbl clk on method to insert code..(check the code in AAA).
7) Save , check and activate the code.
Some useful URL
http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf
http://www.sapdevelopment.co.uk/enhance/enhance_badi.htm
http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b63031e10000000a155106/frameset.htm
Now write a sample program to use this badi method..
Look for BBB sample program.
AAA
data : wa_flights type sflight,
it_flights type table of sflight.
format color col_heading.
write:/ 'Flight info of:', i_carrid, i_connid.
format color col_normal.
select * from sflight
into corresponding fields of table it_flights
where carrid = i_carrid
and connid = i_connid.
loop at it_flights into wa_flights.
write:/ wa_flights-fldate,
wa_flights-planetype,
wa_flights-price currency wa_flights-currency,
wa_flights-seatsmax,
wa_flights-seatsocc.
endloop.
BBB
*& Report ZBADI_TEST *
REPORT ZBADI_TEST .
tables: spfli.
data: wa_spfli type spfli,
it_spfli type table of spfli with key carrid connid.
*Initialise the object of the interface.
data: exit_ref type ref to ZCL_IM_IM_LINESEL,
exit_ref1 type ref to ZIF_EX_BADISPFLI1.
selection-screen begin of block b1.
select-options: s_carr for spfli-carrid.
selection-screen end of block b1.
start-of-selection.
select * from spfli into corresponding fields of table it_spfli
where carrid in s_carr.
end-of-selection.
loop at it_spfli into wa_spfli.
write:/ wa_spfli-carrid,
wa_spfli-connid,
wa_spfli-cityfrom,
wa_spfli-deptime,
wa_spfli-arrtime.
hide: wa_spfli-carrid, wa_spfli-connid.
endloop.
at line-selection.
check not wa_spfli-carrid is initial.
create object exit_ref.
exit_ref1 = exit_ref.
call method exit_ref1->lineselection
EXPORTING
i_carrid = wa_spfli-carrid
i_connid = wa_spfli-connid.
clear wa_spfli.
http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf7940e11d295df0000e82de14a/frameset.htm
and
http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf7940e11d295df0000e82de14a/frameset.htm
Reward points for useful Answers
Regards
Anji
Message was edited by:
Anji Reddy Vangala

Business Add-ins (BAdl) for external ATP system

Hello.
We want to check if it is possible to use following BADI, if we assume that the R/3 is an external System?
You connect an external ATP system by implementing the following Business Add-ins (BAdls):
CRM ATP_EXTERN_BADI for carrying out availability check or availability information using an external system
CRM ATP_EX_POST_BADI for posting the results in an external system
We want to use this BADI in the Internet Sales Scenario, to build our own rule, in order to check if in the whole Company exists enough quantity, independently to the plant. The idea is the customer can receive the information about there is enough quantity to buy or not.
Kind Regards
Rebeca Nieto
P.D.: We are implementing CRM 5.0
Message was edited by: Rebeca Nieto

Hi Martna
please see the below link Parab's check list on ROS.Thanks parab it was a good expalnation on ROS with ros grammer syntax.
you may use client also a different parameter in call structure.
Re: Error installing CE Evaluation April 2007
Web Service ID : ROS
Description: External Web Service in EBP
Bus Type of a Web service : List of Vendors
Display Partner Data again in Vendor List : X
Vendor Root Node : 50000620 (this is Vensor Root node in EBP client)
Use Error Log : X
Use HTTP GET to call Web Service : <blank>
Codepage of Service: <blank>
Techinical type of Service : <Blank>
Logical system : SRDCLNT310 (this is ROs client from there supplier will be transfered)
Path for symbol for service : <blank>
Standard Call Structure Parameter setting as follows
1. <blank> http://....ros_prescreen/main.do URL
2. sap-client 310 fixed_value
3. sap-username dineshp fixed_value
4. sap-password GAJANAN fixed_value
5. HOOK_URL <blank> Return_URL
6. ~OkCode ADDI fixed_value
7. ~target top fixedvalue
8. ~caller CTLG fixed_value
Also defined ROS external web service as default CAT attribute in the organization setting.
BBP_MARKETP_INFO table entry in EBP client.
Hope it helps to configure ROS in define webservices.
regards
Muthu

BBP_TARGET_OBJECTS

Hi,
We're running SRM 5.5(level4) and NW2004s.
We're wanting to create backend reservations under certain conditions. To do this, I've activated BADIs BBP_TARGET_OBJECTS and BBP_EXTLOCALPO_BADI. We've followed the instructions outlined in note 891924 for configuring the number ranges.
Each shopping cart that is created, creates an error in RZ20 - Shopping Cart (number) Error Creating Follow-on Document.
I've tried different things to try and find out why but the error message doesn't tell you why.
I've tried putting a hard break point in the BBP_TARGET_OBJECTS BADI, activated system debbuging and etc.. but I can't get the process to stop in that BADI. This makes me think that it's not being called.
Has anyone experienced this or a similar problem? Are there additional configurations settings to activate this feature?
Thanks,
Jerry

Hi Jerry
I have not tried a hard break point in the BAdI before, but what you can try is to put an infinite loop in the BAdI and enter debugging mode via SM66.
Just another point, you are using BBP_TARGET_OBJECTS?
I believe this has already been replaced by BBP_TARGET_OBJTYPE. You might want to try that.
You can look for the thread: BAdI: Determine Target Object in BE System started by me in this forum for more information.
Regards
Nicholas

EBP 3.0. Restrict Create PO in backend

Dear SRM gurus,
We use EBP 3.0, backend R/3 (4.7 enterprise). We have configuration inplace where a PO is created in the backend, per requirements. However, for one particular vendor, we need to have a minimum price limit set for automatic PO creation, due to additional charges. One option we were thinking is to send it as a PR instead of PO and may be use an user exit for ME59 and combine PR's to generate a combined PO. We also would like to have a check on ME59 to make sure that the minimum prrice is established. Would it be better to do this using condition types in the R/3 or would you suggest any other ways. As for transfering it to R/3 as a PR instead of PO, would it be appropriate to use BADi BBP_TARGET_OBJECTS. If so, would one of you be kind enough to help me with the code. I am not an ABAPer and do not have one available for some time. Any assistance would be greatly appreciated for both on EBP side and on R/3.
Kind Regards,
Reddy

Hi KS,
You can use badi to convert prefered to fixed vendor in your shopping cart.
Thus, you will be able to create a PO in R/3 instead of a purchase requisition.
Please see my answer here :
Re: convert prefered vendor to vendor
Kind regards,
Yann

Error during SC to PO: Recipient not found

Hi Gurus,
I am working on SAP SRM 7.0. The SRM system is configured in such a way all shopping carts (SC) will create a PR in ECC , but according to requirement for some conditions SC will create PO in ECC system. I have implemented 2 BADI's (BBP_TARGET_OBJTYPE and BBP_TARGET_OBJECTS ) to achieve the PO scenario. The PR get created successful but PO creation showing error: "Recipient not found".
Please let me know the probale cause of this error.
Message Class: BBP_EXC
Message number: 004
Thanks,
Prakash Jha

Hi Prakash,
Could you please check if a valid 'Requisitioner' field value is being transferred from the SRM shopping cart to ECC PO.
Cheers,
Yateesh

Condition types from SRM to backend

Hi All,
When accepted bid (complex prices with condition types) is converted to PO, in backend PO is created with net price only. Is there a way to move the condition types also to backend. Can we use any Badi in this case?
Thanks in advance.
Will reward full points for the reply.
Venu

Hi
Either you need to maintain the Condition types locally in SRM system by maintaining Z tables and then create your own logic for pricing in SRM. I guess, this will be much more complex activity.
I know there is some issues, but, Anyways, you have to go for this approach.
You need to go for custom fields and then get the data passed back over to R/3 PO using any of the BADIs
BBP_CREATE_PO_BACK / BBP_TARGET_OBJECTS / BBP_TARGET_OBJTYPE / BBP_CREATE_PO_NEW
in SE18 Transaction.
Refer OSS note - 672960 and 485891 for creating customer fields.
Also, incase this don't suits your requiremnents, Please raise an OSS message with SAP.
Regards
- Atul

Shopping cart Converted to Purchase order directly.

Hello Experts,
 I have a question on what settings to check if the shopping cart created in a system is creating Purchase order directly as Follow-on document. The scenario we are using is SRM 5.0 (Standalone) for Strategic procurement. I checked the BBP_DOC_SAVE, BBP_DOC_CHANGE BADI's but there is no such coding there....any settings in SPRO that is enabling this thing to happen ???
Please let me know about it ASAP. Would definitely reward for useful answers.
Thanks,
Rajeshree

Hi
Couple of reasons can be possible for this ->
1) Workflow is not getting triggered properly. Check workflow configuartion. Are you using standard or customer workflow ?
Seems to me there are no Approvers determined for the particular Product category and Purchase Group combinations, which in turn determines the Approvers (Managers) in this case.
2) Incase the shopping cart dat is complete, and the SRM SPRO system settings are defined to create a Purchase order. Then directly R/3 PO gets created.
3) Check out for all the customer BADI Implementations in SE19 (starting with either Y or Z). Which all are active in this case ? What all code they have ?
4) check out for BADIs especially - BBP_CREATE_PO_BACK
 BBP_CREATE_PO_BACK_NEW
 BBP_TARGET_OBJECTS
 BBP_TARGET_OBJTYPE
5) Check SPRO Settings ->
Here is the path
Supplier Relationship Management -> SRM Server -> Cross-application basic settings -> Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders
Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)
You perform this step only if you create your Materials Management documents in a backend system.
You specify the documents that are to be created in the backend system for a requirement coverage request.
The following documents can be created:
Purchase requisition
Purchase order
Reservation
You enter a product category (such as office supplies, or hardware) and/or an organizational unit. The organizational unit contains the purchasing group that is responsible for procuring products in this category.
You can enter the product category generically, such as Office*.
Note
The backend system is determined using the product category in the requirement coverage request item. The item also contains the organizatinal unit.
You can use the Business Add-In BBP_TARGET_OBJTYPE if you wish to implement a different logic for creating documents in the backend system.
Example
If purchasing group 01 wants to procure materials from the category Raw Materials, a reservation is to be created every time.
If materials in the category PC are to be procured, a purchase requisition is to be created every time.
Activities
1. Enter the organizational unit and/or the category.
2. Enter a source system.
3. Choose the procurement type.
Reservation if stock is available, otherwise external procurement
The system creates a reservation if the material is subject to inventory management and sufficient stock quantity is available in the warehouse on the requested date.
Always reservation for materials subject to inventory management
The system creates a reservation if the material is subject to inventory management, irrespective of whether stock is available.
Always external procurement
The system does not create a reservation, but always procures the item externally. In this case, you specify the type of external procurement.
The following options are significant if the system cannot create a reservation (for example, if there is no stock available or for a non-stock item) or the system must not create a reservation (choose Always external procurement).
Purchase order if item data complete, otherwise purchase requisition
The system always tries to create a purchase order. If the item data is incomplete (for example, the vendor or price is not known), the system creates a purchase requisition from the item.
-> Always purchase requisition
The system always creates a purchase requisition.
-> Always local purchase order
The system always creates a local purchase order.
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Passing Custom fields to Req and PO

Hi,
We are on SRM 5.0 and ECC 5.0.We are using the classic scenario .I am trying to transfer the catalog ID from SRM shopping cart to R3 Req .There are number of threads in this forum that describe the procedure, which i understand.
But now if the Req is converted to PO in R3 either manually or auto, does the custom fields also get transferred automatically ,if i maintain the same custom fields in CI_EKPODB & CI_EKPODBX? or is there anything else i need to do.
Thanks
Raghu

Hi
Besides BBP_CUFMAP, you have to of course :
- create the same Zdata element datain ECC as you have done it in SRM.
- maintain CI_EKPODB with append of your Zdata element
- create CI_EKPODBX and activate it !
Then you will be able to sea your Zdata element (or CUF) in the EKPO table.
You don't need to use BBP_PO_INBOUND !
Re: Update Custom Fields in PO - BBP_ECS_PO_OUT_BADI
Re: Mapping fields in SRM with R/3
Also, Please refer to SAP OSS Notes 672960 and 485891.
The BADIs in SRM which can used in this case, using transaction SE18 are 
BBP_TARGET_OBJECTS
BBP_TARGET_OBJTYPE
In SRM Customization
In the following step : " Go to SRM --> SRM Server --> Cross Application Settings --> Define Objects in Backend System --> go to external procurement and select the function from the drop down box", it says "purchase order if item data is complete, otherwise Purchase Requsition.
Related links for source code and other configuration ->
R3 field is not populated????
implementation of BADI BBP_ECS_PO_OUT_BADI in SRM. and BBP_PO_INBOUND_BADI
Custom field values are not being transfered to the backend system
Re: custom field values not passed to R/3
Do let me know, incase you face any issues.
Regards
- Atul

HR toolbox payroll/Time management step by step

Hi Experts,
              Can you please tell me the PU12 Payroll/Time management step by step process?.
Thanks.

The SAPADPFR process model is designed to launch a payroll and export payroll data to SAP using the Interface with external payroll systems (pu12) transaction. The system creates a process corresponding to the process model for each of the payroll services in the Services menu. In the scenario, ADP-GSI indicates whether the service must use the process model or not. You can copy the SAPADPFR standard process model and adapt it to your companyu2019s requirements.
To launch the SAPADPFR process model, the name of the process model must be entered in the PM_PAIE constant (SAPADDFR by default). Program RPPM0FI creates a link between the different programs run in the process model and the process itself.
The sequence of programs defined in this process model is as follows:
○        OT_SELECT_PERNR_OTFR initializes the process model. The user selects the personnel numbers for the payroll areas pre-selected in a dialog box. The status of the payroll areas considered on Released for payroll is updated in the HRPAYFR_ADP_PERNUM BAdl implemented by ADP-GSI.
○        RPCALCF0 launches the payroll for each employee selected.
○        RPIF00FI creates an export file based on the options defined in pu12 for the FADP interface format.
○        RPPMFLFI calls program RPFL00FI with the file formatting data based on the options defined in pu12.
○        RPTMSEFI converts the file to ZADIG format.
○        RPSENDFI sends the data file to ADP.
The value of the TEM_DVR code affects the following steps:
○        RPDOWNFI extracts the reference values.
○        RPSENDFI sends the reference values.
○        RPPMCDFI deletes the reference values file and indicates the end of the process.
A breakpoint is planned after each program that does not use the PNP logical database:
       1.      to manage return codes as they appear in a ADP scenario: a return code less than or equal to 50 stops the process
       2.      to call the HRFR_PROCESS_STOP_OT_SAPOTFR function module
A conditional breakpoint is planned for management codes. Depending on these codes, it is possible to skip these steps. These breakpoints call the HRFR_PROCESS_NAVIG_OT_SAPOTFR function module.
In the SAPADPFR process model, in the event of an error the process stops on the step following the conditional breakpoint. The function module called allows you to ascertain whether the previous step (STOP_OTFR) was carried out correctly.
A procedure for purging processes is integrated into the FINPER service after the process is closed.
It is possible to view the result of the process and the updated status of the ADP exchange in the exchange table (T5F6K). Program RPDV90FI creates a link between the completed process and the ADP transmission table. You can view this information in the process log for this program.

Creating customer formula to be used in the Query Designer

hi,
How can i code a specific formula to be used in the query designer. As an example, i need to calculate dynamically working days between two dates.
i tried to find the corresponding BAdl interface with no success..
Do you have any suggestion ?
Ludovic

Hi..
I have a scenario ... it may help..
The group HR administrator wants a detailed line item report that lists all employee absences in a given period. The report is to show the employee number, the absence start date, together with the end date of the absence and show the number of calendar days the employee was absent.
The good thing about using this technique is that no redesign work is needed from your technical BW team, no ABAP is involved and best of all, it quick and easy.
Solution:
For this example I created an ODS object called Absence that holds basic employee information along with individual absence record data.
Follow the steps below:
     Open the BEx Query Designer and create a new report on your chosen InfoProvider.
              Drag the Employee, Valid from and Valid to characteristics into the Rows section of the screen.
If needed, apply data selection restrictions to the characteristics as pop up
     Right click on the Key Figures structure and select New Formula
     In the new formula window right click on Formula Variable and choose New Variable
     The Variables Wizard will launch and will require you to specify the variable details.
( Click the NEXT button if the Introduction screen appears )
     Enter the variable details on the General Information as shown in pop up
Enter the Variable Name , Description and select Replacement Path in the Processing by field.
Click the Next Button.
     In the Characteristic screen (pop up) select the date characteristic that represents the first date to use in the calculation (From Date).
Click the Next Button.
     The Save Variable screen (pop up) displays a summary of the new variable.
Click on the Finish button to save the variable.
     Repeat steps first four for to create a second variable for the second date to be used in the calculation.
In the example shown, the characteristic 0DATETO is used to create the variable ABSEND (Absence End Date)
Define the Calculation............
            The new calculated key figure will now show in the columns section of the BEx query designer
excute...
with regards,
hari

BADI for Classic and Extended Classic Scenario

Hi,
   Please   provide list of Reports and BADI's for
       Classic and Extended Classic Scenario.
Thanks,
Srini

Hi,
In SRM there will be a number of BADI's are Available, We can utilize them according to the requirements
As per the request few important BAID are provided below..
Workflows
1). BBP_CHNG_AGNT_ALLOW:          Allow / Allow Change/Add Approver
This BADI is implemented not to allow users to change the approvers in the workflow.
2). BBP_WFL_SECUR_BADI:          Overwrites the authorization level of the approver
This BADI controls the restart of the workflow
Purchasing Related
1). BBP_PGRP_FIND:               Shopping Cart: Determine Responsible Purchasing Group(s)
This determines the responsible purchasing group for the shopping carts.
Shopping Cart Related
1). BBP_SC_MODIFY_UI:          BADI to Change Shopping Cart Layout
2). BBP_GROUP_LOC_PO:          Exit Grouping of Items for Local Purchase Orders
This splits local PO if more than one contract in a PO.
3). BBP_TARGET_OBJECTS:          Exit while determining target objects in backend
4). BBP_WF_LIST:               Change Worklists and Search Results Lists
This is used to restrict the search results for the user.
5). BBP_CTR_BE_CREATE:          Exit when Creating a Contract in the Backend System
6). BBP_CREATE_PO_BACK:          Exit while creating a purchase order in the backend system
This BADI is used to add the shopping carts attachments to the PO and also to make adjustments in payment terms, currency etcu2026
7). BBP_DOC_CHECK_BADI:     General BAdI in Cross-Check for Message Returns
8). BBP_DOC_CHANGE_BADI:     BAdI for Changing EBP Purchasing Documents
9). BBP_ECS_PO_OUT_BADI:     ECS: PO Transfer to Logistics Backend
Thanks
prasad .s

How to activate classic scenario?

Dear experts,
What are the generic settings required to activate classic scenario?Are there other settings required other than below?
1. If extended classic scenario is not activated in global mode:
a. Replicate product categories from ERP backend to SRM system.
b. Define an ERP backend system as the target system for the product categories.
c. Define backend Objects for the product categories (based on Purchasing group and source system).
Does any additional settings required for classic scenario?
2. If there is global activation of extended classic scenario?
a. In such cases, We need to take care of BAdi 'BBP_EXT_LOC_PO' and 'BBP_Det_Logsys'.
Do we need any other additional settings?
Thanks in advance,
Ranjan

Classic scenario is the default scenario unless you have activated the Extended Classic. If you do not need Extended classic then you do not need to activate the Extended Classic and deal with BADI's BBP_EXTLOCALPO_BADI, BBP_TARGET_OBJECTS,BBP_TARGET_OBJTYPE.
If the need is only to implement Classic Scenario accross the board then the steps are good to start with.
Regards,
Surya

Classic Scenario PO not creating, only PR

Hi,
I'm using SRM 5.0, in classic scenario to R/3 4.6C. My Shopping Carts to R/3 are complete, but is not creating a PO. It creates a PR. If i run, ME57, assign and process, PR is already assigned a Fixed vendor, and PO is created without any further data being added. (Vendor, price, etc)
I'm confident my number ranges and Doc Type settings are correct.
In SRM customising, my 'Define Objects in BE Sys, has vaild P.Group, Cat Id, R/3 Source sys, Always external and PO if item data complete'.
When I trace RFC, RSRFCTRC, it is calling BAPI_REQUISITION_CREATE. Not BAPI_PO_CREATE1. Vendor master, set to auto create PO, not using material masters. Mat group and Vendor replicated from R/3 to SRM. Tax is calculated in R/3.
Any help appreciated. Is there a FM in SRM to test why its not creating a PO?
regards Adam

Hi
Couple of reasons might be possible ->
1) Try de-activating all the Custom BADI Implementations using SE19 Transaction (name starting with Y or Z) in SRM System for the time being, and then try out again.
Seems to be some BADI - BBP_TARGET_OBJECTS
BBP_TARGET_OBJTYPE might be over-riding the back-end documents creation.
2) Incase above step, does not help, Try creating a PO or PR directly into R/3 system (using ME21N or ME51N Transactions with the Document typeused in SRM), with the same data that is passed in the RFC call (you traced earlier) then see, what is happening in that case ?
Do let me know.
Regards
- Atul

Badl BBP_TARGET_OBJECTS

Similar Messages

Maybe you are looking for