Document Type UDO - Status

Hi All,
I have a UDO of type Document. A user form is using this object type and having a combo box bound to Status field.
The Close and Cancel are enable for this UDO. Users can directly Close / Cancel the document whenever they want.
My question is, How can I close / Cancel the document using SDK?. I would like to set the document status to Closed if a condition is satisfied.
Using Generic Services, I am unable to set the Status Property. Anybody know a better solution?
Thanks in advance
Anoop

UDO Document can be closed / canceled using SDK.
oDocGeneralService.Close(oGenralParameter);
Or oDocGeneralService.Cancel(oGenralParameter);

Similar Messages

Document type UDO ignoring Period field

Hi all:
I have a document type UDO that includes the automatically created "Period" field which links to financial periods (OFPR). However, apparently I cannot modify it in my form, as no matter what I write into the field the database always ends up with the current period number, instead of the one corresponding to the date I have in my form.
The field is correctly databound as it shows the saved values correctly.
The field is also set correctly by the add-on through code in OnBeforeFormDataAdd before being saved into the database (depending on date selected in a specific field).
The problem is, that even though I am not depending on that field, if the current period is locked, my add-on cannot be used to enter data for another (previous or future) period, because B1 automatically rejects the document when saving ("Period is locked").
Any ideas on this?
Thanks,
Joerg.

I don't have a problem using that field. The problem is that it does not accept what I set it to. It's always saved with the current period number, not the one I tell it to use (the one corresponding to the date used in my UDO document).
As for document type UDO, yes, the add-on is already installed at several clients, I can't just go ahead and change the UDO type. Plus I am using some of the features that come with that type of object (document numbering being one).
As for unlocking the finance period, I haven't tried it but I guess that wold only work if the user has permission to do so, and I couldn't count on that...
Joerg.

Document types Doc status RU can not reach OB or FR - IMG configuration

Hi
A new document status which comes after FR has to be created. I did this but when I create a new document in CV01N, and changed the status until I reach RU, the status which I configured in IMG ánd which is the one before FR, can not be seen and chosen. Do you know how to configure the status that are allowed to come after in the IMG?
Thanks in advance.
Esra

Hi Esra,
when you defined status without prev1 to prev6 values this status is everytime possible (excetion status type primary)
your status-network is RU->FR->OB ?
in status FR prev1= RU
in status OB prev1=FR
or your status-nettwork ist FR->RU->OB ?
in status RU prev1 = FR
inst stauts OB prev1 = RU
your frist status ?? ist type "P" primary with no prev1 value.
This status can be set only one time by creating DIR. So you can define your own statusnetwork!
Hope this will help you!
Regard Wolfgang
Edited by: Wolfgang Gabloner on Oct 19, 2009 4:24 PM

Authorisation combined with document type, activity and status

I want to create a role for a user who is only allowed to create and change document type ZDI in status IW .
Which object authorization can provided this check ?
The object authorization C_DRAW_TCD control only the activity (create/modify) and the document type (ZDI).
The object authorization C_DRAW_STA control only the document type (ZDI) and the status of the document (IW).
But I need the combination of the both authorization. Does a possibility exist in standard to do it without create a client new authorisation?
Thanks in advance for your help.
Amande

Thanks for your response.
But it doesn't works as I want.
The object authorisation C_DRAW_TCS is checked before the save but not after save with the changed values.
for example :
the user has the following authorizations in the modification role:
C_DRAW_TCS activity 02 document type ZDI document status IW
C_DRAW_TCD document type ZDI activity 02
C_DRAW_STA document type ZDI status IW
The user has also the autorisation C_DRAW_STA document type ZDI status FI in the display role
With this configuration the user can modify the document ZDI in status IW and change the status into FI . I don't want that the user can change the status into FI. Does exist a possibility to avoid this?
Of course, after storing this change of the status , the user can't access to the document ZDI with status FI.
SAP doesn't check the authorization C_DRAW_TCS activity 02 document type ZDI document status FI after status change.
Thanks in advance
Amande

Content Server Report- Document types with file sizes & Status history

Hi
We are about to start with implementing Seal Systems, however we are a global company with to start with 4 content servers in different regions of the world. In order to determine bandwidth for future strategies, I need to know what is stored on each content server in terms of document types, type file and size of files attached to each document type and of course date created and status changes of each document.
In addition we are of course contemplating usage of SAP Cache servers, not only for better responses, but also for backup purposes.
What we are using is SAP ECC 6 with the content servers using MAX DB. I have contemplated creating a Z program in order to return only the required information for import in Excel where I can then manipulate the returned result to a report which fits us.
But before I start with this, does anyone know of any report or tools just to do that within SAP? I have seen these capabilities in other PLM solutions.
I would appreciate any feedback in this regard
with friendly regards
Joe Kosterman

Hi Joe,
maybe transaction DB20 could help you here.
From DMS side tables DMS_PHIO2FILE and DMS_PH_CD1 are most relevant for original data stored in Content Server.
Regarding the changes of documents report MCDOKABL will show you all the changes done for a specific document.
For maintaining and monitoring content repositories please see transaction CSADMIN.
Best regards,
Christoph

How to add a document type for the residence status GB in infotype 48

Hi Team,
How to add a document type for the residence status GB in infotype 48.
Please answer this at the earliest.PFA screnshot.
Thanks
chris

I believe there is a PDF doc which comes with the component (it should be at your harddrive when you install it), which describes everything you will need.
In a nutshell, there are two types of relationship: sibling - sibling, parent - child (there are some more nuances, but it follows the same logic).
A relationship is created between two existing items (not sure, if you can also create a relationship for a new checked in item, but it would be just a usability). You select the type of relationship and the item - I believe depending on the relationship you may start from either item. The dialog to start is INFO (display metadata) or UPDATE (update metadata).
When a relationship is created you may watch it also from either end (again INFO is the starting point).
It is quite self-explanatory, so if you have the component installed you may just play around with it for a while and that is it.

Material Statuses based on the Purchase order Document type

Hi Experts,
We need to maintain the Plant material status based on the purchase order document type.
Example - If I am using NB for normal purchase orders and ZB for STO procurement then, there should be a material status which should give warning message - 'do not use ' for ZB STO purchase orders and it should allow to create NB purchase orders for that same materials.
Please advise what are the possibilities?
Thanks
Regards
MM

Hi Gurus,
Thank you for your reply, Please find my replies below
@@ - Mallinath - We need this restrictions for some type of materials ( with specific Material types) which should not be procured through inter company STO process, buying plant should use the normal purchase. for other Material types they should be able to use the inter company STO process.
@@ DEV - We are already using the Spl. Procurement keys for inter company STO process.
Example - Material type ZXYX should not use the inter company STO process, but it should be allowed all other processes.
Please advise how we can control this process?
Thanks
Regards
Raja

How to delete a document status for a document type

Hi,
May i know how to delete the some document statuses for a document type. Because present we are having many document statuses, In that we want to remove some statuses.please find the screenshot and help me please.
In tha above screenshot, Now i want to keep the highlited one only. Remaining status i want to delete. May i know how to delete and after deleting the statuses, may i get the statuses as per my requirement.
Regards,
Mastan.

Hi,
As per the above requirement, i have deleted some statuses, But now i want in cv02n, the following statuses,
In first step, i have changed the status in cv02n, from work request to Reallocation status. please find the screenshot.
After this step, i want get the status in cv02n, as PPC head Status, But while changing status, i am not getting the status pop box as per my requirement and i got as per below pop screen.
Please guide me how to get the status of PPC head in pop box when clicking the Document status icon. And also please guide on that, if i am deleting the existing statuses, what i need to check.
Regards,
Mastan.

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

CREATION OF NEW DOCUMENT TYPE

Dear cons
We want to create a new document type for pur. requisition.In this document type account assignment will be 'P'(PROJECT) . w.b.s should be only enter.
so pl. give the details of filling data in the required field step by step. waiting for your early response.
thanks
nirupama

Hi,
In order to create a document type for a purchase requisition use the path
spro-materials management - purchasing--purchase requisitions --define document type
in that screen you select the document type you want to copy to create your document type and perform the action.
if you want to change the screen/field selection for your document type select the field selection key (if you select the document type as NBB the field selection key will be NBB.,and go to the screen and change the field status.
Hope this will be suffient for your requirement.
Regards,
Raghu.

How to define certain document type (BKPF-BLART) for certain movement (101)

Sometimes ( I think it is becuase of the tcode) certain purchase 101 movements create a WA type FI document and some other times purchase 101 movements create WE type FI documents. I have seen a table ( accessing from omba transaction) in which for diffenent tcode´s we have either WE or WA. If we always use migo transaction why sometimes in bkpf we have migo_tr, migo_gi, ....;....
How should I do in order to create always WE FI documents for purchase 101 movements?
Thanks in advance.

Check the settings in SPRO-MM-Inventory Management-Number assignemnt-Define number ranges for accounting documents.
Here you assign accounting document type to tcodes.
Normally , WA is used in receipts for MB1C/MIGO_GI tcode - for e.g for 561 mvmt type.
SAP recomends keeping this setting as it is.
SAP help text copied here for reference:
Define Number Assignment for Accounting Documents
In this step, you set the number ranges for the accounting documents which are created when goods movements or inventory differences are posted.
Accounting documents in inventory management
For accounting-relevant goods movements, the system creates two different documents:
material document
accounting document
Both the material documents and the accounting documents have their own document numbers. When inventory differences are posted, the system also creates an accounting document for the physical inventory document.
In this step, you only maintain the number assignment for accounting documents.
Document types
Accounting documents are split into document types to allow differentiated document number assignment, which is the basis for distinguishing between the various accounting operations. A number range is assigned to each document type. In a company code, you have to define number intervals for each number range and fiscal year.
In inventory management, the transaction determines which document type is used.
Example: Goods receipt for purchase order
Requirements
You have already defined the company code.
Default Settings
In the standard SAP System, the following document types are predefined for inventory management:
WA for goods issues, transfer postings, other goods receipts
WE for goods receipts with reference to purchase orders
WF for goods receipts with reference to production orders
WI for inventory differences
WL for goods issues with reference to deliveries (SD)
WN for net posting of goods receipts
PR for revaluation documents
Each document type is already assigned a number range. In company code 0001, number intervals are defined for each number range both for the current and the previous fiscal year.
Number range 49 with the year-related interval 4900000000 to 4999999999 is assigned to the document types for all goods movements, except goods movements with reference to purchase/production orders.
Document type WE is used for goods receipts with reference to purchase orders and production orders. This document type is assigned number range 50 with the year-related interval 5000000000 to 5099999999.
Please note that net postings of goods receipts (document type WN) are not active in the standard SAP System. If you want to post goods receipts net, you have to assign document type WN (instead of WE) to the transaction MB01.
Document type WI is used for posting inventory differences. This document type is assigned the number range 01 with the year-related interval 0100000000 to 019999999999.
SAP Recommendation
Activities
1. Check whether you can use the standard settings.
2. If not, you have to add new document types to satisfy your requirements:
a) Define a new document type under Financial accounting document
b) types.
c) Assign a number range to the document type.
d) Under Financial accounting number ranges, define the year-related number intervals for the given number range in your company code. If you do not want to use the year-related number assignment method, enter 9999 in the Year field.
e) Under Allocate document type to transaction, assign the relevant document type to the transaction codes of inventory management.
Document type PR (revaluation documents) is already assigned.
Notes on transport
You transport number range objects as follows:
Choose Interval -> Transport in the accounting document Number Range screen.
All intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.
Dependent tables are not transported or converted.
All other activities are linked to the automatic transport.
Edited by: Saurav on Jan 24, 2011 6:03 PM

Creation of new document types for document splitting rules

Hi experts,
We have copied from existing SA document type to new document type.
In standard SAP SA document type - define document splitting rule, we have select "NO INHERITANCE OF ACCOUNT ASSINGNMENT", when posting the GL document SA document type without mapping partner profit center,system is control the derive the partner profit center.
Our requirement is copied from existing SA document type to create a new document type - we have created the new dusiness transaction variant and we have map the "classify document type to document splitting rule " and we have selet the "No inheritance of account assignment" while posting in FB01 GL document with out mapping partner profit center system is not control the " derive partner profit center".
Could you please assist us as soon as possible
Thanks ,
Sreenivas
Edited by: sapfico.srini12 on Jan 16, 2012 4:37 PM

Hi,
In order to create a document type for a purchase requisition use the path
spro-materials management - purchasing--purchase requisitions --define document type
in that screen you select the document type you want to copy to create your document type and perform the action.
if you want to change the screen/field selection for your document type select the field selection key (if you select the document type as NBB the field selection key will be NBB.,and go to the screen and change the field status.
Hope this will be suffient for your requirement.
Regards,
Raghu.

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

Report on Deleted Parked AR Documents with 'Z' status

Hello Experts,
Any suggestion to obtain the list of deleted parked AR documents which did not get posted in the past. We created AR documents and were not sure about VAT treatment and were parked but later managed to invoice the customer separately. Subsequent to this, we have deleted the parked AR document and I know when these parked document gets deleted, document numbers are marked by a letter 'Z' and you can get a report BY DOCUMENT NUMBER. Is there any standard SAP report that can be run BY CUSTOMER to see all deleted parked documents for that customer only.
Appreciate valuable suggestions to achieve the above.
Rgds
CONMJI

Hi,
use S_ALR_87012293 - Display of Changed Documents to check the deleted parked docuements or any status regarding parked document.
Here if you select park doc radio button and give input document type and posting key, then you will get the customer/vendor/GL related docuements . Take that dump and put in the table and give input of your customer code.it will shows those documents if any.
Thanks
ANJI

Purchasing Document Type (Purchase Order and Contract)

Dear all;
I have created two different PO document type in development Server .I have transferd sandbox for further testing ,There i hve change the number range interval status to "0" after that I have created a PO with new document type in the sand box ,it is working fine but after save ,system showing some error msgs. as Below
Express document "Update was terminated" received from author "JOYDEEP"
What may be the problem.kindly suggest .
Thanking you;
Regards;
Joydeep Mukherjee

This update termination may be due to some configuration or may be due to some development which is resulting in the dump. Go to SBWP - your SAP inbox, there you will see a mail, open that mail to see the details for the reason for this update termination.

Document Type UDO - Status

Similar Messages

Maybe you are looking for