Restriction of GR & IR for PO with specific document type

Hi,
How we can restrict doing Goods Receipt & Invoice Receipt for a Purchase order, instead they do the payment directly for the Purchase order item in FI. We need to restrict GR & IR for PO with particular document type.
Regards,
Srinivas

Hi,
Yes i do feel the same. Normally if a PO is created means system expects a GR and and IR .If you do not expect the ir means it is a free entry.
But however you can control the GR / IR through account assignment .please check the account assignment definition at SPROMMPUR-Account assignment-AAcategory.
Once the PO is created with account assignment the procurement is for consumption (non stock)
if it is a stocked procurement system will check the GR/IR indicator in the PO.
When a PO is created in MM module and the cycle is not completed , it will always show as open PO.I think the context for FI direct posting will be differrant.
Regards,

Similar Messages

Restricting Sales Order Creation for Customers with specific AccountGroup

Hi
We have 2 Accont Groups for Customers namely Actual & Prospective.
We wish to allow Enquiry / Quotation and Order creation for customers with Account Group ACTUAL and wish to allow only Enquiry and Quotation creation for customers with Account Group as Prospective.Is there anyway i can apply Sales Order creation block on an ACCOUNT GROUP on whole and not on Individual customers...
Regards
Sanjeev Bagaria

Hello
I did this through Listing Inclusion / Exclusion.
(1) We created a new Customer Group 99 for Prospective Customer
(2) We then created a new Condition table xxx with Customer Group & Material Type(as footer)
(3) We then created this new Access Sequence Customer Group / Material Type to Exclusion Procedure B00001
(4) We then assign the Exclusion Type B00001 to Sales Documents ZDOM & ZEOR our Order Sales Documetn Types
(5) And finally we created a record for Exclusion with 99 Customer Group and Material Type as FERT..
This now restricts creation of Sales Orders for all my Prospective Customers provided Customer Group is maintained in Customer Master. We are now also able to make Enquiry / Quotation and Sample Sales Order for Prospective Customers sicne we have Different Sales Document Types for all these and have assigned Exclusion only to normal Sales Order Document Type.
Thanks a lot for all the suggestions provided.
Regards
Sanjeev

How to Restrict Single Delivery Date for PO with Multiple Line Items

Dear Experts,
How to Restrict Single Delivery Date for PO with Multiple Line Items.
System needs to through Error Message if User Inputs Different Delivery Dates for PO with Multiple Line Items in ME21N Tcode.
Can we achive this by Some Enhancement in SAP or Not ???
If so how to do it.
Any Inputs is highly appreciated.
Thanks and Regards,
Selvakumar. M

Hi Selvakumar,
we can resrict the PO to have a single delivery date in all the line items by means of giving a error message or overwiting the delivery date keyed/determined in the line item.
You can use the BADI -> ME_PROCESS_PO_CUST. In which you need to implement the method PROCESS_SCHEDULE.
(for technical aid - This method will be called for each and every PO line item, From the imporing parameter im_schedule we can get all the details of current PO line, even we can change the data in the current PO line. )
Regards,
Madhu.

Restrict display and posting for specific document types

Hi,
Is it possible to restrict display and posting for specific document types? I want to restrict authorization to SM document type in FS10N, and KSB1 tcode. Please help
Best Regards,
KIRAN.

Sandipan Choudhury wrote:
FS10N checks for this object ("Check" in Su24) but when user doesnot has this authorization object he gets access to all doc types and when the user is restricted to specific doc types (object present in user's authorization) he will get access to only those doc types. This is how the authorization check for F_BKPF_BLA works, in other words this authorization is Optional.
Sorry, but this is not true and seems to be an invention of how you would like it to work...
The coding works like this (generally):
    if sy-subrc ne 0.
      select single * from t003 where blart = postab-blart.
      check sy-subrc = 0.
      blrtab-blart = t003-blart.
      blrtab-brgru = t003-brgru.
      append blrtab.
    endif.
    if blrtab-brgru ne space.    "<--- important condition!!
      authority-check object 'F_BKPF_BLA'
           id 'BRGRU' field blrtab-brgru
           id 'ACTVT' field actvt.
      if sy-subrc ne 0.
        rcode = 4.
      endif.
    endif.
endif.
The "optional" aspect is whether or not the document type has an auth group on it in T003, failing which the check is suppressed.
If it reaches the check, then it found something and then checks that selected value.
Moral of the story:
--> Do not believe SU53.
--> Do not make assumptions from ST01 traces.
--> Read the documentation carefully.
--> Read the code to see how it really works (you can jump to the coding location from the trace).
Cheers,
Julius

For STO with Doc. Type UB, shipping instruction not picking automatically..

Dear All,
For STO with Doc. Type UB, shipping instruction not picking automatically.. Please advise.
Regards

Hi
Please verify in the config the below is populated already....
SPRO -> Material Management --> Purchasing --> Purchase Order --> Set up Stock Transport Order --> define Shipping Data for Plants
Open the Recieving & Shipping plant ID's and maintain their own shipping data and save.
Maintain: Sales Org:
Distr Channel:
Div:
Aside: your shipping plant is already configured with Sh.Point - Tcode: OVL2
Regards
RG

Ledger Group vs. Ledger Specific Document Types

Can anyone tell me the value in having a document type that is purely used for tracking accounting principle specific adjustments (GAAP Adjustments / STAT Adjustments / IFRS Adjustments / etc.)? If you already have various ledger groups hitting various accounting principles using a standard accounting document why would you need a ledger specific document type and when would it be used in normal business transactions instead of using a ledger group / standard accounting doc type combination?

HI,
In my company I set up IFRS-leading ledger, 2 local ledgers for each comp. code.
Accounting key-user found it easier and more traceable to make ledger specific postings using one special doc.type / number range for each ledger (group). "normal" doc. types can only be used to make posting in all ledgers assigned to each comp. code.
With this setting they can easy identify ledger group specific postings from postings happened to all ledgers using the same account number.
But,as you mentioned, its not really necessary to do so.
BR Christian

Assignment of billing document type with accounting document type

Hi
I need one information regarding SD Billing Document type assignment with accounting document types.
Here CRM people asking me where we can see if the Billing doc type is BV( Cash Sale) accounting document should be RV
Just go to T.Code VOFA for Billing document types. Based on this only system generate the Accouning documents RV, AB so onu2026u2026.
But how it is determining this accouning document type they want to know.
Pls advice

In VOFA where it says Document type enter the FI doc type they want to post to. Otherwise it defaults to RV.
pls assign pts to say thanks.

Issue With Sales Document Type in BW.

Dear Experts,
I am facing an Issue with Sales Document Type(Object name is 0DOC_TYPE).
when i am loading data from R/3 to BW It is converting Sales Document type as follow
Sales Document Type in R/3                         Sales Document Type in BW
OR                                                                        TA
CR                                                                        G2
DR                                                                        L2
I check with an ABAPer and he told that there is conversion exit for this Object so that's why it is converting when sending to BW. But the user wants to see in Report same as it is in R/3 like OR, CR DR ... etc.
I have done some investigation and found that the conversion exit (CONVERSION_EXIT_AUART_INPUT and CONVERSION_EXIT_AUART_OUTPUT) are converting the values based in the table TAUUM
The staructure of TAUUM is
MANDT(Client) SPRAS(Language) AUART(Sales document type (not converted)   AUART_SPR(Language key for sales document type)
and values are
100 E TA OR
100 E G2 CR
etc....
The same Conversion exits(CONVERSION_EXIT_AUART_INPUT and CONVERSION_EXIT_AUART_OUTPUT) and table TAUUM are available in BW as well. So i thought I can Use InfoObject 0DOC_TYPE by changing it's conversion Routine as AUART(which runs based on the above mentioned conversion exits).
but the the problem is table TAUUM(Pool Table) does't have any data in BW.
So can anyone tell me is there any option to load data into table TAUUM from R/3 or any other option to solve this issue.
Your ideas will really help's me.
Thanks in advance,
Dara.

Hi Venkat,
Thanks a lot for your immediate response.
The InfoObject 0DOC_TYPE was without conversion exit by default. but when data coming from R/3 it is converting and sending to BW So that's why i am planning to use conversion exit "AUART" in the info Object.
I checked data in R/3 using RSA3 it is showing sales document type as "OR" and for the same transaction data when i checked in PSA it is showing as "TA".
Could you please let me know if there any other options.
Thanks in advance,
Dara.

APP - F110 - Payment of multiple invoices with different document type

Hi
Vendor X has been assigned with payment method same with two document types. One document type got 4 invoices and other document type got 1 invoice.
During payment run (F110) for each document type, the system picked up both the document type but listed them as two separate lines in the proposal list. When we process the payment the system also created two payment documents.
Is there a way for these two document types to be processed as a single proposal and payment.
Any suggestion how can we process these invoices together in a single proposal/payment document?
Thanks & Regards,
Sam

Thanks

Vendor Payment with different document types

Dear Sapguru,
We have a scenario where a particular vendor payable is in two different document types for example, RE and KZ.
When we execute TC F110, the payment proposal is grouping the payments by document type. I.e. it grouped all the documents under type RE and grouped all the documents under type KZ and created two line items in the payment proposal.
Actually, we want to have a single group consisting of all the document types payable to the vendor.
We have checked different SAP notes and also verified out system settings, but the problem still remains.
Can somebody let us know how to group all the open items in a single line item in F110 irrespective of document types.
Thanks in Advance.
Regards.,
Rama

Dear Naravi,
the main factor which affects the grouping of items is the Structure ZHLG1:
ZBUKR
ABSBU
LIFNR
KUNNR
EMPFG
WAERS
ZLSCH
HBKID
HKTID
BVTYP
SRTGB
SRTBP
XINVE
PAYGR
UZAWE
DTWS1
DTWS2
DTWS3
DTWS4
KIDNO
All these fields have to coincide, to have a single payment.
Please check why two documents with different document type are paid into two different payments.
Read the SAP notes 109233 and 164835 and 305414 as well.
I hope this helps.
Mauri

Purch grp linkage with PO document type

Hi Gurus,
Is there anyway to link purchase group with PO document type. e.g Consider RM & PM as the purchase grps. Let ZRM & ZPM be the PO document types. I want to link the two such that the system should allow only ZRM when you choose RM purch grp & similarly for PM. It should not allow to create for other document types.
Thanks & regards,
Kumar

Hello,
I am afraid that this functionality is not there in standard SAP as far as my knowledge goes.
What you can do is, Create a Z table with 2 fields one for purchasing group and the other for the document type. Enter the allowed document types against each purchasing group in the table. This table should be called by an user exit while saving/ entering the PO. If the PO's purchasing group and the document type does not match the records in the Z table, then an error message can be thrown. Please check with your developer about the user exit that can be used for this process.
Regards,
Sakthi

Document types for Entry view Vs document type for General Ledger view

Dear experts...
Can you explain what is the deference between Document types for Entry view and document type for General Ledger view?
Dasu

Hi,
Document Types for Entry View
In this activity, you define your document types. Document types are used to differentiate the business transactions and to manage how document are stored.
Document Types for General Ledger View
You define for non-leading ledgers the document types for the documents in the General Ledger view. At the same time, you assign for each document type a number range to be applied in the     assignment of document numbers:
    o   You do not need to make these settings for your leading ledger
        because, in the case of this ledger, the document number in the
        entry view always corresponds to the document number in the general
        ledger view.
    o   You only have to make these settings for any non-leading ledgers
        that have a fiscal year variant that differs in at least one company
        code from the fiscal year variant of the leading ledger in this
        company code. In this case, the document number in the entry view
        does not correspond to the document number in the general ledger
        view and you have to define a separate document type with document
        number assignment for the general ledger view.
        For all non-leading ledgers that, in the company code to which the
        postings are made, have a fiscal year variant corresponding to the
        fiscal year variant of the leading ledger in this company code, the
        document number in the entry view always corresponds to the document
        number in the general ledger view.
        Note
        The need to define a document type for documents in the general
        ledger view depends only on whether the fiscal year variant of the
        non-leading ledger in the company code (to which the postings are
        made) differs from the fiscal year variant of the leading ledger in
        this company code.
Regards,
Kiran

I need output type NEU automaticaly for create purchase order document type

Dear Experts,
I need output type NEU automaticaly for create purchase order document type NB
when transaction code MN04, I am doing the following:
(1) I selected the third option Purchasing Output determination: Document type
(2) I selected the output type NEU.
(3) In condition records in document type , i have chosen NB.
(4) In name its automatically coming as Purchase requisition
Please suggest how Purchase Order NB will come

Hi,
Check & press F4, NB Purchase Order (for catagory F) will be there after entering PO output type NEU & then maintaion the condition record in MN04.
Output type NEU automaticaly defaulted during purchase order creation with document type ,then just fine tune the output (message) type in following path:
SPRO--->MM->Purchasing>Message>Output control->Message types> Define message type for Purchase Order----->Fine-Tuned Control: Purchase Order
Now here select the check box corresponding to your output(message) type NEU to have print output automatically displayed & save.
Now try to creating Purchase Order & you will have default message type NEU.
Regards,
Biju K

Making condition type mandatory for a particular po document type

I have 2 po document type namely local po and international po. i want a particular condition type ZLCS to be picked automatically as soon as the user picks the po document type.

Hi,
   You may check the condition technique through a new condition table with PO document type. You may proceed as below:
   You may append the standard MM condition structure to include the PO document type field (in structure KOMPAZ), with the help of abapers . Add the field to condition catalogue in the path: OLME - Conditions - Define Price Determination Process - Extend Field Catalog for Condition Tables.
    Now, you can create condition table with document type field in M/03. Maintain the condition table in the access sequence in M/07. Assign the access sequence to condition type in M/06. Include the condition type in pricing procedure. Maintain condition record for the condition type with required document type in MEK1.
    Check the procedure and revert back in case of any doubts.
Regards,
AKPT

Posting of MIRO transaction with other document type

Hi Every Body,
We want to make MIRO with other document type for some particular transaction , not with RE , we have defined other document type VR , also number range but how to link it in MM part because MM number range same for RE and having provision for only one number range . Can we define MM no. range also separate & other wise with same MM no. how we can linl VR doc type no. range..
Please give some idea
Thanks,
Dharmveer

Hi,
Thanks for reply
We mapped the system as suggested by you , but we get posting termination most of time while doing MIRO & changing document type VR in deatil tab in header part.
Please suggest me, hoe we can create transaction variant of MIRO then we can process such activites apart from standard.
Thanks,
Dharmveer

Restriction of GR & IR for PO with specific document type

Similar Messages

Maybe you are looking for