Urgent: backend PO/PR doc type

Hi,
I am confused and need to check!
Currently we have configured the transaction type for backend doc in users attributes. this doc type is for backend PR (ABP). config says if complete then PO otherwise PR..back end PO doc type is ACBP and it is not set in attributes
when we order SC having valid source (R/3 contract) it auto picks up PO doc type ACBP in one system and creates PO. Is this doc type coming from R/3 doc type linkage or any other place. Pls help
Alok

I could find the mapping done in the PO change BADI..But I would like to ask, is there a standard function like giving both doc type in the attributes or only way is to configure the same doc type in R/3?
Thanks!
Alok

Similar Messages

Bidding - Create PO in backend with multiple doc type.

Dear Friends,
We are working on Bidding Cycle with classic scenario where we want follow-on document Purchase Order to be created with more than one document type.
So we defined
BSA attribute with ZPO & ZSRM and
DP_PROC_TY attribute with ZPO & ZSRM.
Due to DP_PROC_TY we are able to see two options for "Transaction Type for Purchase Order" (ZPO and ZSRM). However the PO is getting created with only one document type ZSRM.
Am i missing any step in between?
Or could this be a bug?
Regards,
Sandeep Parab

Hi,
See whether the foll note helps:
Note 1059053 - BBP_BID_INV:Transaction type from quotations not taken in PO
Else you can refer the suggestions given in the foll thread:
Re: BE_DOC_TYPE => ECPO
BR,
Disha.
<b>Pls reward full points for useful answers.</b>

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

Very urgent, vendor down payment clearing - ka doc type

hello gurus,
while clearing vendor down payment, some down payment entries are posted as ka doc type. now i have to clear the invoice down payment with the ka doc type. how to do this.
for retention account we booked in special G now that retention money also paid but that doc is not showing as cleared. still it showing in red colour. but balance is nill. what to do for this..
can anybody help me very urgent friends
thanks
jaya

HI ,
CHECK THI SPROCEDURE ,
DOWN PAYMENT;
Vendor A/C--a DR1
TO Bank
Invoice;
Expence a/c dr
to Vendor----
2
down payment clear:
Vendor A/C-----Adr -
3
to Vendor a/c----4.
Hi once you do the Down payment clearing only 1 & 3 line items will be cleared.
but 2&4 line items will show as open items .
This line items you have to clear .Clear this in F-44.
CHANDRA

New sales doc. type scenario-Urgent

Hi all,
I have got a scenario:
A customer complaint order type has to be made which will take the reference of a Billing doc. Now, based on that Customer complaint order type, Credti memo request and returns order going to be made.
I have made a customer complaint order type Zcut and maintain Item category as Zcat.
In vov8, i have maintained:
created no. range for the doc. type
Check reference mandatory field with "M"
Billing Block field with "06" sign & approval.
In vov7, i have maintained:
Billing relevance "F'
Pricing "X"
I have also maintained copycontrol measures between Biiling doc. and sales doc. with VTAF and between Sales doc. & Sales doc. with VTAA.
Now, when iam creating this doc. type with reference to the Billing doc. , it is not doing following things:
1.no customer name, quantity, amount is getting copied
2. required del. Date is coming as mandatory
can anyone give solution for it. it is urgent
Thanx in advance,
Sourav

Pls check..for VTAF
=>Header level--between ur billing type which i assume is F2 and complaint SO e.g. ZCUT
three routine
DataT 052 Billing doc.header----use for data transfer from VBAK
DataT 103 Bus Data Hdr Billing---use for copying business data
DataT 003 Bill.header partner-----use for copying business partners
=> At item level u wll see TAN which i assume ur using while issue goods..duoble click on TAN...in new screen
ur "ItemCat Proposa" at target sales doc type ZCUT should have ZCAT ie ur return item category
also check following routine
DataT 153 Item from BillingDoc-----use for VBAP data transfer
DataT 104 Bus Data Item Billng-- --use for business data transfer at item level
DataT 004 Bill.item partner-----use for business partners transfer at item level
Copying requirements    303 "Always an item"
Pos./neg. quantity         Blank
Pricing type                  D
Regards
Jagdish

Anybody ever created multple PO doc type/number ranges in extended classic?

I have searched this forum, and found plenty of useful threads which would help me determine different document types/number ranges for back-end purchase orders in a classic scenario. (And I have done something similar many years ago on a classic EBP 3.0 implementation)
However, I have a customer who has an SRM 5 extended classic implementation, and who (Based on certain simple criteria) requires a different PO number range to identify certain types of indirect orders. (They also have direct materials procured using doc type ECDP, but that's not relevant to this requirement)
This would obviously have to apply to the local PO in SRM, as well as the backend ECC PO.
It would also need to be derived for orders created automatically via approved shopping carts, as well as those orders that are created via sourcing.
I've copied ECPO via define transaction types IMG step, as well as assigned a new number range.
Just to test, I've also added the second doc type in the BSA attribute for a particular test user - just initially see if it was possible to manually choose when creating a PO in sourcing. However, I could only get ECDP and ECPO.
I have looked at various BADIs to see if I can determine doc type or number range somewhere in the PO creation, but as far as I can see, they either:
- Seem to apply only to the object type (PO, requisition, reservation etc) rather than the transaction type within that object.
- Or look like they are too late in the process to influence the doc type and number range (BBP_DOC_CHANGE_BADI?) ... which doesn't seem to have those doc type or PO number fields available anyway
- Or I doesn't seem to be trigerred at all when turning requirement into Po and ordering via sourcing. (tried break-point & endless loop in implemnetation of BBP_CREATE_BE_PO_NEW, but nothing happened. In any case the PO number was alreadya ssigned)
If anybody has ever managed this before, or can tell me that I am definitely barking up the wrong tree, it would be gratefully appreciated. The document type is actually lesss important than the different number range... and was really just an attempt to trigger a different number. I'm starting to think that this sort of thing may only be possible in a classic implemntation.
What I need ideally, would have been some kind of 'local PO' equivelent of the BADI that enables you to determine transaction type for a bid.
Regards,
Vince
Edited by: Vincent White on Dec 6, 2010 5:13 PM

Hi. Not sure on this, but I can tell you that with extended classic it is BADI BBP_ECS_PO_OUT_BADI that is called for the backend PO instead of the CREATEPO_BACK BADI.
You can have a look in BBP_ECS_PO_OUT_BADI and see if that helps?
Don't think it will influence the PO in SRM at all though.
Have you tried the number range / grouping BADIs? They definitly work for changing the number range for classic POs.
Regards,
Dave.

Drop Down for Selecting the doc type while uploading?

Hi all,
Is it possible to create some document type in KM so that we can select the doc type and upload the file to specific folder.
What I mean from Doc type is like Doc for Meetings, Doc for activity report.
Is it possible using standard KM features? Urgent help needed pls reply.
Pls send the document regarding this to [email protected]

Hi Karan,
I'm not sure if I have understood your issue correctly, but let me try:
1. You want to upload documents to KM
2. Uploading them, you want to categorize them in some way, so that they can be identified as docs for meetings, docs for unit XYZ, etc..
3. After upload, you want each doc to end up in a folder according to its category
If this is what you want, try the following:
1. Create a custom resource property called "category" or something similiar.
2. You may define your possible values for that property. This makes it a drop down box containing the possible values in property view. (You can see property view when uploadinga document)
3. Mark the property as searchable
4. Create a taxonomy using TREX searching your repository for the given values of your custom property
Now you can upload documents, fill the custom property, and some minutes later TREX will create a link to the document in the specified 'category folder'.
If you need some more detailed assistance, please come back.
HTH,
Carsten

Cannot find sales doc type data in my report on the multiprovider

hai everone,
I'm doing report on the multiprovider which is connected to different ods's i'm getting the data for all the fields except for 'sales doc type'.I could see the data for it in the ods on which the multiprovider is built but could not find the data in the report.Can any one suggest me how to get the data for sales doc type into my report.
Urgent..

yeah listcube is a TCODE to check the data in the cube. run the code and enter the same selections that you would be doing on a query to see and see if it returns any data. if it does, then the problem is with the identification. Most of the times create recommendations work like a charm. But just go into the chars and see if the IO in question has been checked against the ODS that aint returning any records.

Event 50 doc type 30 is not for incoming payment in tcode fpe1 fscd module

Dear Experts
i had configured a new company code and done the necessary configuration changes in the FSCD collection and disbursement module but while posting a document in FPE1 in FSCD i am unable to post a document .
At present i am getting the following error for the document" Event type 50 : Doc type 30 is for incoming payment
Kindly help me urgently as i am stuck up on the issue
Regards
Devendra Mohan

Payment document can be posted based on the accounting document.
If you want you can maintain invoice number in reference field, also there is one option to make reference field mandatory.
In OBA7 activate reference document number as mandatory for the document type DZ. So, while doing the transaction in F-28, value should be mandatory to this field.
If maintain invoice value in reference field, then you can do sorting and totaling based on the reference field in FBL5N.
there are no standard reports to check the outstanding amount based on the invoice number.
Rgds
Murali. N

Validation for doc type for f-43

Hi,
I Have created a validation for document type sk for t.code f-43, while creating validation i have taken fb01 it is working fine for f-43 at the same time which is working for f-02 also it should not work for f-02.what to do please help me
Thanks and Regards
Radha

Hi,
Almost all FI transactions other than the clearing transactions, may apparently have different names like F-02, F-43 etc, but at the backend there is only one mother transaction code FB01. So any validation on FB01 will impact all FI t-codes.
I would suggest that you use document type in the validation, if you can have clear demarcation between the doc type used for different transactions.
Cheers.

Error during determn of backend follow-on doc. for shopping cart

I am using Classic Scenario in SRM 4.0 and R/3 ECC5.
When I am making PO in SOCO against approved shopping cart I am facing following error and PO is not getting created.
"Error during determn of backend follow-on doc. for shopping cart XXXXXXXXXX"
I have Checked up following :
1. Product Cat defined in backend and in Org plan attribute
2. Object for Prod Cat Vs. PGR defined in SPRO
3. Doc type in R/3 attribute defiend in BSA attribute of Org Plan.
Still problem is coming.
Any clue form some one.
Sanjay

Hi Sanjay/Vadim,
We are also having a simialr issue..
for SRM server 500 SAPKIBKS08...
R/3 4.7
"But this issue comes up only in the Test system and works fine with the Dev sys.." Double checked all the config steps and looks alike..
We are using the classic scenario RFx process to create a backend PO from the bidding engine after the bid is accepted..
it alwayz throws up the error SC/ Local Error..
: Error during determn of backend follow-on doc. for shopping cart 0010000103 / 0000000001....
we just started debugging from the web by breaking it at META_BAPI_DISPATCH and still looking into it..
but in the mean while just want to know if this is more a config issue or and RFC connection issue..
could you forward me any OSS notes if any regarding this issue..
thanks in advance..
Regards
Manoj

Doc Types in Contract Management

All,
is there a standard way to distribute Contracts / Scheduling Agreements based on a SRM GOA (Release 4.0 as well 5.0) without maintaining the corresponding Doc Types (GCTR) in R/3? Client expects that the standard R/3 Doc Types (LPA / MK, WK) are linked to a SRM GOA.
Looking forward to your thoughts!
Thanks,
Claudia

Hi
Refer to these links as well.
PO line item displaying incorrectly from contract
BBPV_CONTRACT_CREATE
Code needed for contract BADI's
Need Help in editing an existing Contract
BAPI_CUSTOMERCONTRACT_CHANGE for update pricing
Addition of custom fields in Contract and mapping it with the fields in SRM
Contract Upload to New System
Position Field Costumer in Contract
Source determination in backend (R/3) for distributed contract i.e. GOA
Regards
- Atul

I Doc type INVOIC02

Hi,
We are using INVOIC02 I Doc type for intercompany transactions.
Whenever we have an intercompany transaction within the country the IDoc was created successfully.
When we have an intercompany transaction for export customer, IDoc was created, but the accounting document in IDoc is not created. It is throwing a messaage no F5 566: specify tax jurisdiction key. We are maintaining the tax jurisdiction code in customer as well as supplying company.
What will be the reason for the error message. the message type is INVOIC.
Can any one throw light on this issue. Urgent yaar
bye
Venkat.

hi Venkat ,
For foreign trade there is a message type EXPINV for export invoice.
and IDOC EXPINV02 .
Do check into this message type for export customer.
Reward if helpful.

KR doc type posted without vendor line item a mandatory item category

Hello Gurus,
We have SPL document splitter activated in our ECC system. We have the business transaction variant 0300 / Z001 assigned to doc type KR. The vendor line is obligatory in the above business transaction variant (BTV). THe splitting rule is also assigned for this BTV.
THe problem is that despite having the vendor as obligatory for this BTV, we are able to post the doc type KR (vendor invoice) without the vendor line item e.g.. doc with doc type KR and debit and credit to expense a/c.
Please share your experience if anyone has come across this issue,
Prakash

Hi,
To make the vendor line mandatory for KR document type, you can write the validation as below:-
Step 1:-
Create a message ID via transaction code SE91 for message class /EACC/MSG/ACC_COMP as you want to display to user.
Step 2:-
Go to transaction GGB0 and create the validation step at complete document level in Financial Accounting as below:-
Pre Requisits:-
BKPF-BLART = 'KR'.
Check:-
Create a exit code using user exit and check that line items have at least one vendor line item.
For this take the help of ABAPer and create a copy of the program RGGBR000 and code your check here and assign to the application area GBLR in view V_T80D via transaction code SM30.
Message:-
Message created in step 1 as error message.
Step 3:-
Please also check that this validation has active status (Status=1) at line complete document level (level 3) for your company code in transaction OB28.
Regards,
Gaurav

Changing doc. type after creating a doc. type.

Hi Friends,
We are doing our time ageing from the time of creating the document in DMS. We created a document with particular doc. type wrongly, after two days we found that the DMS creation was done with wrong doc. type. In this how to transfer to new correct doc. Type, if we delete this & create a new we canu2019t get any info that it was created two days back.
We made Z report for this time ageing report.
Regards,
Sai Krishna

You cannot change the document type after the document has been created. The only way to do this would be with an enhancement and this would create major issues with the integrity of your system

Urgent: backend PO/PR doc type

Similar Messages

Maybe you are looking for