Document type to purch org

Hello guru's
I want to restrict the certain document types for some purch organisation while creating PO. is it possible, if yes how can i...????/

Only restriction possible on document type is based on item category. Restriction based on P Org looks difficult.
One way could be an enhancement to throw error message while creation of PO.

Similar Messages

PO document type selection

Hi Experts,
SRM 7 EHP 1
ECC 6 EHP 5
PPS through CPPR (classic scenario)
Purchasers create RFx and receive bids against the RFx. Once the bid is accepted, PO is to be awarded.
We want to have an option of selecting the ECC PO document types while creating the PO through 'Create Purchase Order' option in the bid. We have maintained the ECC PO document types in the org. structure against BSA attribute but still do not get an option of selecting the document type.
Please advise.
Thanks & Regards,
Amish

Hi Amish,
You are trying to run PPS (Procurement for Public Sector) in Classic Scenario.
PPS is only supported in ECS(Extended Classic Scenario.Hence this scenario will not be possible.
For more details refer http://help.sap.com/saphelp_srm70/helpdata/en/c9/8d47ed4a5548c08521615d84a590e6/content.htm
Hope this helps.
Best Regards,
Vinita

Document type and Transaction type

Hi,
Can someone give me a clear and detailed understanding of how to maintain transaction types in SRM system and document types in the backend system based on various scenarios (i.e standalone,classic. extended.....)
Is it mandatory that the document type assigned in org plan attribute BSA be maintained in the local system as well??
Thanks
sunny

Lol Sunny,
Thanks for the compliment, but no, I'm in france. I work on SRM for now 5 years, so it helps
In fact META BAPI are only BAPIs, with a certain way of developping: What SAP calls "Abstraction Layer".
This allow you to manage Partner system version differences, and backend unavailability, the process is:
->META_BAPI
-First try synchronously
-->Read table BBP_FUNCTION_MAP (and now get into BADI) to get the exact function module to be called depending on the partner system type and its version
--->Call of this function (which either makes local actions, or call the backend system with RFC)
If the system was unable to call the partner system , it creates a job to re-try the call (based on what you entered in customizing).
Here is the SAP description:
<i>- Depending on the release level used, you can use various Business Application Programming Interfaces (BAPIs) to implement the business processes in the back end system. The abstraction layer encapsulates the BAPI calls in the back end system that are necessary to generate the back end documents from requirement coverage requests. The abstraction layer accesses the following sources of information:
-Dispatcher: This function module analyzes the Customizing settings and then knows:
--     Which driver it must call
--     Which back end system it is communicating with
--     The back end system release
--     Driver: For each release level supported and each abstraction layer, there is a driver module that calls the BAPIs in the back end system.
--     Spoolers: The spooler controls the transfer of documents from the Enterprise Buyer system to the back end system. If errors occur during the transfer, for example, the back end system cannot be contacted, the spooler is used as the queue for the requirement coverage requests. The spooler tries to contact the back end system at regular intervals and to transfer the documents.</i>
Regards.
Vadim.
PS if you are really "amazed" please be more generous in your rewards

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

Urgent: User Roles assigned to Sales Orgs and document types

Dear Guru's :
I have job user roles one side and sales orgs on otherside. We are trying to find out which sales orgs are using what sales document types.
All i am trying to achieve is connect those two and make a report. it needs to be done by SE16
First step is :
PFCG- Enter Role u2013Click glasses-Authorizations-Display Authorization data
you need to identify the authorization objects for each T-code and then assign the appropriate values for each authorization object. these authorization objects assigned to a Role and then, allowed T-codes are assigned to Role and
My Basis Person to Create one AUTHORIZATION OBJECT V_VBAK_AAT Sales Document: Authorization for Sales Document Types and assign your required transaction codes to that authorization and assign them to the users.
User IDs which can use this Role (set of authorizations) can be assigned to this role.
Second step is achieved through SE16 ;
Execute this two table :
There is no one-shot for this However there is a way out for this outside SAP.
You can download AGR_1251 and AGR_1252 for the selected roles and use MS Excel or Access to do this compare for you. Its a bit more tricky than said, however once you get a hang of it, I think its a good way of reducing the efforts of making use of individual compare reports.
Any one knows how to do this i am kind of lost here. Could you help me to organize this process / steps.
Full points will be given to who helps me answer my question.
Thank you in advance.

Dear Raghu and all:
I am very much thankful to you for your answer Raghu. This is exactley what i was looking for. Could you throw more light on this topic. Or do you know where can i get more info.or more tcodes related to this topic. I am using SUIM and PFCG. I dont know much about this transactions. Could you please help me to understand this topic.
I have Authorization object through which i found out which sales documents are attached to users. I dont know next step in this process. Or does any one know any thing about this subject. Any help will be grateful.
Van bills.

Invalid combination of Sales org,document type,division

Hi Gurus,
I entered sales area in the salles area header but when when i am entering customer it is saying
"Invalid combination of Sales org,document type,division "
Can anybody tell the reason of it.

Ensure that both the material code and customer code are created in the same sales area. To check this, go to MM02, key in the material code, select any sales view and check in which sales area, the material has been created. Similarly, go to XD02, key in the customer code and below you can see a tab "Customer sales area". Click that so that you can see in which sales area, the customer has been created.
thanks
G. Lakshmipathi

Sales document type is not defined for(sales org/division/distribution chan

Hi Friends,
I am getting the error that sales document type is not defined for x/y/z(sales organisation/division/distribution channel). while creating sales order.
Any pointers will be rewarded.
Regards

Hi there,
When you define a sales doc type in VOV8, you also should assign that to the sales area SA (sales org / dist channel / division).
Only then you will be log a sales order for a sales area.
Check if you have done it. You will find it in SPRO --> Sales & Distribution --> Sales --> Sales doc header --> Assign sales doc type to SA.
Regards,
Sivanand

User status profile assigned to document type in specific sales org.

Hi,
can anyone tell me, if it is possible to assign a user status profile to the combination sales document type and sales organization?
Maybe with some kind of enhancement and/or user-exit?
Best Regards,
Florian

Hi,
You may use the following user exit to determine the relevant status profile with specific sales organization (VKORG) (There is no standard way is available to do so)
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
regards
Vivek.
Edited by: Vievk Vardhan on Jan 12, 2010 2:46 PM

Supplier not intended for purch. org.

Hi Experts,
I have a problem during creating the shopping cart. We're implementing registration of supplier scenario with SUS(sus system is in different client of SRM) We've succesfully registered the supplier.But while i'm creating shopping cart, system gives error message " Supplier 0000000272 not intended for purch. org."(272 is SUS registered supplier). I've checked business partner from the manage business partner transaction(from the web) and i can see related purchasing org. record(i'm trying to create shopping cart for standalone scenario). I've checked customizing settings for product category. Also tried to create shopping cart with another supplier. But got same error. can you please help?
Regards,
Fırat

Hi Muthu,
My vendor group attributes are:
Accounting System for Vendor     VENDOR_ACS     T90CLNT090
Catalog ID                                     CAT
Company Code                             BUK     3000     T90CLNT090 ( ECC Backend)
Company Code                             BUK     3000     SRMCLNT001(SRM system)
Current ITS for an External Partner     EXT_ITS     http://arete05.arete.com:8000/sap/bc/gui/sap/its/
Current ITS of User                       ITS_DEST
Local Currency                            CUR     USD
System Alias for Vendor                    VENDOR_SYS     SRMCLNT001
System Alias for Vendor                    VENDOR_SYS     T90CLNT090
Tolerance group                            TOG
my organizational attributes of local purchasing organization are:
Account assignment category     KNT     AS
Account assignment category     KNT     CC
Accounting System for Vendor     VENDOR_ACS
Approver for Value Limit                     SLAPPROVER
Asset Class                                     ANK
Asset Subnumber                             AN2
Attachment                                     AN1
Catalog ID                                     CAT     ros_prescreen
Commitment Item                            ACC_CMITEM
Company Code                            BUK     3000     SRMCLNT001
Company Code                            BUK     3000     T90CLNT090
Cost Center                                    CNT     1000     T90CLNT090
Cost Center                                  CNT     4140     T90CLNT090
Current ITS for an External Partner     EXT_ITS
Current ITS of User                          ITS_DEST     http://arete05.arete.com:8000/sap/bc/gui/sap/its/
Default printer                               PRI     LP01
Delivery address                            ADDR_SHIPT
Document Type in R/3 System     BSA     EC     T90CLNT090
Document Type in R/3 System     BSA     PO     SRMCLNT001
Flag: Forward Work Item              FORWARD_WI
Funct. Area                                     ACC_FCAREA
Fund                                            ACC_FUND
Funds Center                                    ACC_FCENTR
Generic Account Assignment (Standalone)     STR
Grant                                            ACC_GRANT
Invoice Recipient Address            ADDR_BILLT
Local Currency                            CUR     USD
Maintenance plant                           PM_SWERK
Movement type                            BWA     201     T90CLNT090
Network                                         NET
PM Material Group                        PM_WGR
PM Plant of Component                     PM_WRK
PM Purchasing Group                   PM_PUR_GRP
PM Purchasing Organization            PM_PUR_ORG
PM: Proposed G/L Account           PM_GL_ACCT
Phase                                          PM_IPHAS
Planning Plant                               PM_IWERK
Plant for Work Center                  PM_ARWRK
Plant of Responsible Work Center     PM_VAWRK
Request                                           ANR
Request type                                   PM_AUART
Requisitioner                                   REQUESTER
SAP Smart Forms: Company Logo     SF_GRAPHIC
SAP Smart Forms: Footer          SF_FOOTER
SAP Smart Forms: Header         SF_HEADER
Sales Order                                  AUN
Sales Order Item                          APO
System Alias                                 SYS     SRMCLNT001
System Alias for Accounting Systems     ACS     SRMCLNT001
System Alias for Vendor                 VENDOR_SYS
Tolerance group                            TOG
Transaction Type: Contracts             CT_PROC_TY
Transaction Type: Create PO Manually     DP_PROC_TY     EC
Transaction type: Description     TEND_TYPE
User role     ROLE                           SAP_BBP_STAL_EMPLOYEE
User role     ROLE                           SAP_BBP_STAL_SECRETARY
User role     ROLE                            SAP_BBP_STAL_VENDOR
WBS Element                                    PRO
Thanks in advance
Fırat

Restrict the user   based on document type on migo transaction-prepare GRN

Hi,
We are running ECC6.0 R/3 system.We had a requirement as follows
In MIGO transaction , we want to restrict the user on document type i.e. we want that a particular user can prepare GRN for document type STO only. He cannot prepare GRN for other document type.
We checked SU24->maintain check indicators for transaction codes->enter migo->execute->check indicator.This returned us the authorisation objects present in Migo transaction.We checked the help of all these objects,but none of them we found suitable for above mentioned requirement.We were planning to find out the proper authorisation object to add to Profile generater.
The following is the objects which we have checked for.
A_B_ANLKL-->     Asset Postings: Company Code/Asset Class
A_B_BWART-->     Asset Postings: Asset Class/Transaction Type
B_USERSTAT-->     Status Management: Set/Delete User Status
B_USERST_T-->     Status Management: Set/Delete User Status using Process
C_AFKO_AWK-->     CIM: Plant for order type of order
C_CACL_DSG-->     Interface Design
C_DRAW_BGR-->     Authorization for authorization groups
C_DRAW_DOK-->     Authorization for document access
C_DRAW_TCD-->     Authorization for document activities
C_DRAW_TCS-->     Status-Dependent Authorizations for Documents
C_KLAH_BKP-->     Authorization for Class Maintenance
C_STUE_BER-->     CS BOM Authorizations
C_STUE_WRK-->     CS BOM Plant (Plant Assignments)
C_TCLA_BKA-->     Authorization for Class Types
C_TCLS_BER-->     Authorization for Org. Areas in Classification System
C_TCLS_MNT-->     Authorization for Characteristics of Org. Area
F_BKPF_BUK-->     Accounting Document: Authorization for Company Codes
F_BKPF_BUP-->     Accounting Document: Authorization for Posting Periods
F_BKPF_KOA-->     Accounting Document: Authorization for Account Types
F_FICA_FOG-->     Funds Management: authorization group of fund
F_FICA_FSG-->     Funds Management: authorization group for the funds center
F_FICB_FKR-->     Cash Budget Management/Funds Management FM Area
F_KNA1_APP-->     Customer: Application Authorization
F_LFA1_APP-->     Vendor: Application Authorization
F_SKA1_BUK-->     G/L Account: Authorization for Company Codes
G_GLTP -->       Spec. Purpose Ledger Database (Ledger, Record Type,
                               Version)
J_1IDEP_SL-->     Authorization object for depot sale transaction
J_1IEXC_OT-->     Authorization object for Other Excise Invoice Create
J_1IEX_PST-->     Autorization object for posting Other Excise invoice
J_1IGRPT1-->     Auth. for PART1 at GR
J_1IINEX -->            Incoming Excise Invoice
J_1IRG23D-->     Authorisation object for Depo Transactions
K_CCA-->                     CO-CCA: Gen. Authorization Object for Cost Center
                                Accounting
K_CSKS     -->                CO-CCA: Cost Center Master
K_CSKS_SET-->     CO-CCA: Cost Center Groups
K_PCA-->                    EC-PCA: Responsibility Area, Profit Center
L_TCODE-->                    Transaction Codes in the Warehouse Management System
M_ANFR_BSA-->     Document Type in RFQ
M_ANFR_EKG-->     Purchasing Group in RFQ
M_ANFR_EKO-->     Purchasing Organization in RFQ
M_ANFR_WRK-->     Plant in RFQ
M_BEST_BSA-->     Document Type in Purchase Order
M_BEST_EKG-->     Purchasing Group in Purchase Order
M_BEST_EKO-->     Purchasing Organization in Purchase Order
M_BEST_WRK-->     Plant in Purchase Order
M_MATE_CHG-->     Material Master: Batches/Trading Units
M_MATE_STA-->     Material Master: Maintenance Statuses
M_MATE_WRK-->     Material Master: Plants
M_MRES_BWA-->     Reservations: Movement Type
M_MRES_WWA-->     Reservations: Plant
M_MSEG_BMB     -->Material Documents: Movement Type
M_MSEG_BWA-->     Goods Movements: Movement Type
M_MSEG_BWE-->     Goods Receipt for Purchase Order: Movement Type
M_MSEG_BWF-->     Goods Receipt for Production Order: Movement Type
M_MSEG_LGO-->     Goods Movements: Storage Location
M_MSEG_WMB-->     Material Documents: Plant
M_MSEG_WWA-->     Goods Movements: Plant
M_MSEG_WWE-->     Goods Receipt for Purchase Order: Plant
M_MSEG_WWF-->     Goods Receipt for Production Order: Plant
M_RAHM_BSA-->     Document Type in Outline Agreement
M_RAHM_EKG-->     Purchasing Group in Outline Agreement
M_RAHM_EKO-->     Purchasing Organization in Outline Agreement
M_RAHM_WRK-->     Plant in Outline Agreement
Q_TCODE     QM -->         Transaction Authorization
S_ADMI_FCD-->     System Authorizations
S_ALV_LAYO-->     ALV Standard Layout
S_BDS_DS-->     BC-SRV-KPR-BDS: Authorizations for Document Set
S_BTCH_ADM-->     Background Processing: Background Administrator
S_BTCH_JOB-->     Background Processing: Operations on Background Jobs
S_CTS_ADMI-->     Administration Functions in Change and Transport System
S_DATASET-->     Authorization for file access
S_DEVELOP-->     ABAP Workbench
S_DOKU_AUT-->     SE61 Documentation Maintenance Authorization
S_GUI-->                     Authorization for GUI activities
S_OC_DOC-->     SAPoffice: Authorization for an Activity with Documents
S_OC_ROLE-->     SAPoffice: Office User Attribute
S_OC_SEND-->     Authorization Object for Sending
S_PACKSTRU-->     Internal SAP Use: Package Structure
S_PRO_AUTH-->     IMG: New authorizations for projects
S_RFC-->                     Authorization Check for RFC Access
S_SCD0     -->                Change documents
S_SPO_DEV-->     Spool: Device authorizations
S_TABU_DIS-->     Table Maintenance (via standard tools such as SM30)
S_TCODE     -->                Transaction Code Check at Transaction Start
S_TRANSLAT-->     Translation environment authorization object
S_TRANSPRT-->     Transport Organizer
S_WFAR_OBJ-->     ArchiveLink: Authorizations for access to documents
V_LIKP_VST-->Delivery: Authorization for Shipping Points
V_VBAK_AAT-->Sales Document: Authorization for Sales Document Types
V_VBAK_VKO-->Sales Document: Authorization for Sales Areas

Have you executed a trace while a functional user executes the transaction code for the specific parameters? (i.e. document type). The trace will then show which objects are being checked; then look at the object documentation in txn Su21 to determine if there are any ways to restrict on the particular value; in some cases, if the authorization group field is being checked, additional configuration is needed in order to implement the security (Su21 will explain in detail for the particular object).

Sales document type restriction to create sales order

Hi Frinds,
My client has one requirement ...they have different sales document type. For sales document type free of charge delivery they want only some authorised person should be able to create sales order. Is it possible to set the authorisation to create sales order according to sales document type.
Regards
SV

Yes,
As already suggested, it is very well possible to restrict the user for the use of certain sales document type from basis.
& to add to the above,
Create Z* table with Sales Org + Doc type = UserID.
call this table in VA01 transaction & write piece of coding , if current USerID have entry in this table with the said combination - should not allow to proceed further.
without any basis involvement also you can ahieve your requirement.
Note: Sales Org is used for validation purpose only.
Regards,
Reazuddin MD

PO document type for third party PO...?

Hello friends,
My client's requirement is that third party PO should have different document type, say ZTRD?
I tried to configure the same with PR and PO doc types. I created new PO type ZTRD. I maintained the combination of PR doc type NB with item cat S to PO doc type ZTRD with item cat S. I also deleted the standard config i.e. combination PR doc type NB with item cat S to PO doc type NB with item cat S.
I created third party SO which created third party PR (doc type NB). But when I tried to convert this PR into PO, still with above config, I am getting error - Doc. type/item cat. NB/S (requisition) <-> NB/S (purch. order) error.
Please help me to configure the Z doc type for third party PO.
Thanks in Advance,
Pat.

Hi
Please try the following, do not delete the standard settings
1) Create Z document type for PR and assign this document type to relevant Schedule line Category ( CS for example) in SD
2) Create Z document type for PO and keep only Item category S & Z document type for the Item category S created for PR.
Hope it helps.
Thanks/Karthik

PO's Document type created from Shopping Cart

Hi all,
I work on a SRM 5 system with Extend classic scenario.
when I create a PO from a SC, the system assign automatically a document type.
I have to change this assignment.
I already define transaction type for BUS2201, but I'm not able to find where the assigned doc type from SC is.
Thanks
Enzo

Hi Enzo,
The P.O in SRM has document type has either ECPO or ECDP.
These document types are assigned in the attributes of the root org.
The attributes you maintain in the root org for document types are :
BSA & DP_PROC_TY
You can find the possible document types in SPRO > IMG > SRM > SRM Server > Cross Application basic settings > Define Transaction types
Choose BUS2201 (Transaction category) and click on the Transaction types in the Dialog Structure on the left side. There you can see ECDP & ECPO transaction types.
Hope this makes you more clear. Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

PO document type for automatic PO is transportation module

Hi,
I am generting automatic POs through transportation module. I am able to assign plant, P.org and P. group through transportation planning point for automatic PO but it is always creating PO of NB type. Is there any configuration where I can change the PO type for automatic POs in transportation?
Thanks & Regards,
Yuvnish

Hi
Check the path :-
IMG-->Material Mgt. -->Purchasing --> Define default Values for Document Type.
Regards
Amitesh Anand

Document Type Not Found in Shift Note Settings

Dear gurus,
I'm implementing Ecc-dimp function, shift note report.
I check in PRD SPRO configuration:
Logistics General -> Make Settings for Shift Note, I have made one Shift Note Type "MS".
The settings from DEV Server (transport) is "DMO", but when I browse (F4), there's error "Document type DMO cannot be used".
I've CORRECTLY configured the document type in DMS in production (used by MM consultant for MARA attachment).
Then I check the settings in DEV server, and browse (F4) on the same configuration.
There's only one document type which can be used, that is "DMO"
Here's the error in PRD system:
[http://postimage.org/image/bjyus8a3x/]
Is it some SAP bug?
Thanks for help.
Best Regards,

We're running ECC 6.0 EhP4.
Technical component is 7.01 level 0009
Business software component is 604 level 0009
Latest kernel patch
Regards,

Document type to purch org

Similar Messages

Maybe you are looking for