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

Similar Messages

Business Transactions and Document type

Hi eXperts !
Can anyone please explain these business transactions like when they are created, what is the document type related to these and which one should I use to see the Amount paid to the Vendor (Actual Payment)
KOAE     Actual Settlement CO External
RFBU     FI Postings
COIN     CO Interface
RKU1     CO Act. Primary Cost Transfer
KOAR
Actually I need to extract a report in Project systems with actual amount paid to the vendor + all the actual cost but it shows only down payment (doc. type KA if i am not wrong) not the final payment.
Also please explain these document types because i can see them in my report but I dont really know what does it mean.
AA     Asset posting
AB     Accounting document
KA     Vendor document
TZ     Vendor Document
KZ     Vendor payment
SA     G/L account document
KG     Vendor credit memo
As these things can be better explained by FICO guys so I decided to put the question here, Thanks alot !
Rabiee

Thanks for the reply AP
I'll check KZ doc. type
what about other document types and business trans. ?

Separate Transaction event key and Document type

Hello Gurus,
Need suggestion and process how to have separate transaction event key and Document types sued in Material document creation with a different number range for the movement types used for SD processes.
Example: 601/602/651 movement types have the Transaction event key as WL
               561 has the Transaction event as WA
               701/702 movement types have the Transaction event as WI
the transaction event keys of WA WH WI WL WQ WR WS WZ have the same number range.
I am looking for solution and suggestion as how do we maintain transaction event key and document type for SD dispatches, cancellation, returns movement types separately.
Thanks and Regards

Hi,
   U can create new document type in OBF4 copy the existing on ee.g WA make new document type and in number range assign the FI number range which u want to assign, MM number range can be create in T. code OMBT and FI number range in FBN1. Documen ttype assignment to t. code is done in OMBA
regards,
zafar
Edited by: zafar_karnalkar on Aug 13, 2010 12:23 PM

Exise Transaction type and Document Type for part 2 record created by J2iun

Hi All ,
We utilized available credit of SERVICE TAX (HCESS and ECESS) and CENVAT (of both RG23A and RG23C) credit against payable SERVICE TAX ( ECESS and HCESS).
At the time of save , system has generated accounting document.I have checked generated accounting document which is perfect.Here the document type selected by the system is ED.
But when I check corresponding part2 entry (in table J_1IPART2) there system has not updated any value in fields Exise Transaction Type (TT) and document Type while internal document and Financial Year are updated with 0 value.
I am not sure if system behaves in the same way for J2IUN generated PART-2 entry.
I need your help to understand it.
Regards
Shrey

Hi,
There is not any transaction type for Excise Utilization and determining the accounts of the fortnightly utilization.
The credit account of the transaction type u2018DLFCu2018 is used as the debit account here. For the credit side we pick the debit accounts from the GRPO, EWPO and TR6C transactions.
This is the reason system only generates a Part II Serial No and updates in table.

Posted a transaction with FBS1 and FB01 of document type AC.

Hi Guru's
It's urgent
I posted a transaction with FBS1 and FB01 of document type AC. What could be the difference between these two transactions.
Regards
Odaiah Pelley

Hi
What's the description of the Doc Type AC
as for info:
FB01 is a normal GL invoice entry for a cost that is incurred as per the posting date specified at the time of entering the invoice
FBS1 - is used for Accrual postings which in acctg terms would be a cost incurred for a long term contract which will be distributed periodically
hope this helps..
Rukshana

Business Transactions and Document Types

Hi eXperts !
Can anyone please explain these business transactions like when they are created, what is the document type related to these.
KOAE     Actual Settlement CO External
RFBU     FI Postings
COIN     CO Interface
RKU1     CO Act. Primary Cost Transfer
KOAR
Actually I need to extract a report in Project systems with actual amount paid to the vendor + all the actual cost but it shows only down payment (doc. type KA if i am not wrong) not the final payment.
Also please explain these document types because i can see them in my report but I dont really know what does it mean.
AA     Asset posting
AB     Accounting document
KA     Vendor document - This type of doc. is created when we do Down-payment to vendor (correct me if m wrong)
TZ     Vendor Document
KZ     Vendor payment - Doc. created when we do Actual Payment to vendor (correct me if m wrong)
SA     G/L account document
KG     Vendor credit memo
Rabiee

Any thoughts ?

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).

Authorization based on plant and Purchase order document type

Hi
My client has a requirement wherein a user will have authorization for transactions only in his plant. But only for Purchase order document type UB (Stock Transport Order) the user should be allowed to create for all plants.
In short, if Purchase order document type is UB, should be allowed for all plants
if Purchase order document type is NB, should be allowed to only one particular plant.
My Basis person says that such a restriction is not possible.
Kindly suggest me on how to provide a solution to this.
Thank U.

Hi,
This is possible.In this case you need to create two seperate roles.
1)Create purchase order for all plants (This can be used in long text)
2)Create purchase order for <plant no> plants.
For case 1:--
i)Populate field BSART of M_BEST_BSA with UB.
ii)Populate field WERKS of M_BEST_WRK with '*'. SAP reccomends to fill up organizational data through organizational level tab only.So while doing this step you need to put * from organizational level tab only.
For case 2:--
i)Populate field BSART of M_BEST_BSA with NB.
ii)Populate field WERKS of M_BEST_WRK with 'plant no'.
Dont worry about the objects i mentioned those are maintained through SU24 and will be automatically pulled once you insert ME21 transaction code.
Let me know if it helps.
Thanks,
Aveek

Purchase Order Document Type and Account Assignment

Hi ,
We have a requirement to control Account Assignment in Purchase Order Item line based on the Document type selected on the Purchase Order header.
Like if user selects Purchase Order document type "ZNB" (Customized created) , then he will only able to select "K" or Blank or "P" as account assignment and similary we want to limit other Account assignments based on the Purchase Document type.
How can we make this Control settings?
Regards
Shrey

Hi,
You can't really limit the account assignment categories per document type, at least not directly.
You can limit the item categories that can be used for a document type via configuration:
Materials Management > Purchasing > Purchase Order > Define Document Types
Within this transaction you can define which item categories are valid for a specific document type.
You can then define which account assignment categories are valid for each item category
Materials Management > Purchasing > Account Assignment > Define Combination of Item Categories/Account Assignment Categories
BUT
limiting the account assignment categories that are valid for an item category will affect ALL purchase order document types that this item category is valid for. And you can't create your own item categories as this is a SAP standard table that can NOT be altered.
Regards,
Monika

Change default document type in transaction F-47

Hi guys,
any idea how may I change the default value (not on user level) of the document type in transaction F-47.
Thanks and regards

Use transaction OBU1 (path: IMG Financial accounting / general ledger accounting / business transactions / G/L account posting / Carry out and check document settings / default values)

Document type to be set blank in transaction code mr41,mrhr

Hi,
I want to set document type and currency field as blank whenever the user go for the transaction MR41 and MRHR. At present whenever user enter transaction MR and MRHR these two fields display some value which is there in memory id, i want to set these field as blank instead of getting the value from memory id. Please help me out if there is any solution.
Regards
karan

Hi,
Good morning and greetings,
Go to the transaction Code OBU1 and make the default Document Type for the transaction code MR41 and MRHR as Blank and the system will not propose the Default Document Type for the same...If you dont want the user to use a document type from History disable History in the SAP GUI options...Hope this meets your requirement.
Please reward points if found useful.
Thanking you
With kindest regards
Ramesh Padmanabhan

Different Document Type for a standard transaction

Dear all,
Iu2019m facing the following problem: I wish to set a different Document Type for a standard transaction.
In the specific, I need a different DT for Reverse Document (T-code FB08) instead of standard SA.
Is that possible?
Thanks in advance
Alberto

Go to OBA7, click on doc type of the original document (which I guess is SA) and then update the field "Reverse Doc Type" to the doc type you want to.

Different Document types for Reciepts and payment-Cash Journal

Hi Gurus,
Please tell me how can we make different document types for reciepts and payments in cash journal and where we need to assign it??
Please revert asap.
Thank You

Hi
While posting the transactions by using FBCJ T.Code u can select the Receipts or Payments or Expenses then the documents will be genereted. FBCJ02 is the T.Code for no.range there u can assign the no.range intervels.
Shammi

Limit document types for transactions

Hi Sapper's,
Besides using a validation, is it possible to limit document types for certain transactions Eg. FB60 - Doc Type KR and KA and KG ONLY.
Cheers

Hi
You can create a transaction variant for FB60 using trancode SHD0, select the document type and make it output display only.
This would prevent the users from using a different document type.
Hope this helps
Deepa

Multiple PO document types/transaction types in Extended Classic scenario

Hi All,
We are on SRM_SERVER 550, Extended Classic Scenario.
We have a requirement where we need to create multiple PO document types (based on certain criteria).
I have noticed that in standard, there are only 2 transaction types provided for SRM PO - ECPO and ECDP.
We need more document types and these should be triggerred automatically after SC is approved.
I understand that we need to maintain all the PO transaction types in SRM, number ranges in SRM then maintain the same transaction types as PO document types in R/3 and same number ranges in R/3.
I also understand that the change for document type needs to be done in BBP_DOC_CHANGE_BADI.
I have 2 specific questions:
1. We need to maintain attribute BSA for the users. Here we need to mention the document type and source system. What should be the source system mained in attribute BSA for ECS? Should it be the SRM system or R/3 system?
2. In BBP_DOC_CHANGE_BADI to change the PO document type/transaction type in ECS scenario, which field should be changed? Should it be ET_ITEM- BE_DOC_TYPE?
Regards,
Srivatsan

Srivatsan,
To create new transaction type:
Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Define Transaction Types
To create new number range:
Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Number Ranges --> SRM Server Number Ranges --> Define Number Range for Local Purchase Orders
You can define to create automatic PO when a SC was created in: Supplier Relationship Management --> SRM Server --> Sourcing --> Define Sourcing for Product Categories
Rgs,
Pedro Marques

Document type and Transaction type

Similar Messages

Maybe you are looking for