Hide PO-Type in Enjoy-Transaction

Hello,
exist there a possibilty to hide PO-types in the ME21N drop down list?
We use one PO-Type for an automaticly process.
The user should not choise this PO-Typ manuelly.
Can i manipulate the output or is there only the possibility to block this PO-Typ in an user exit?
Regards

Ralf,
Now I got ur question..
please control it in authorization for - "Document type in Purchase order"
M_BEST_BSA
BSART
Instead of * give only the allowed Document types ( here exclude the doc type used for automatic process).
Once this is excluded from authorization object then users will not have access to that doc type.
Basis consultants will do it.
Regards,
Uzair

Similar Messages

Enjoy Transaction screen -FB70

Hi,
We are in ECC 6.
How to change the Screen ( Header text is to be activated)
How to do it ?
Appreciate yr early answer.
Regards, Chitras

Do the config steps:
IMG-Financial accounting-GL accounting-GL account posting enjoy-Define doc type for enjoy transaction.
Here press new entries
Enter ur company code
Account type as S -GL account
Trans- leave blank
Doc type- SA
Then go to document type OBA7
Flag the document header text if it is not already flagged.
Now do the posting in FB50, system will prompt you to enter the header text.

Config to hide "Mvt type " field in MIGO

Hi ,
Can anyone suggest me the necessary config to be maintained to hide the "mvt type " field in the upper right hand corner which appears by default when we get into transaction MIGO .
Thanks in advance

Why do u want to hide Movement Type Field?
Anyways you can hide it by going SPRO>MM>IM>Settings for Enjoy transactions>Feild selections for MIGO

Table control in Enjoy transactions like FB50/FB60/FB70

Hi,
I am using enjoy transactions like FB50/FB60/FB70 which provide me the facility to enter more than one GL Accounts in a very easy manner.
The screen looks like a table where we can enter the data very easily.
Now we can hide and display fields in enjoy transactions using the Table Settings button.
This button is provided at the right most corner of the section where GL accounts can be entered.
If the curson of the mouse is placed at this button the decription "Configuration" will appear.
Now when I click on this button and click on Administrator button, I will get the fields which can be made invisible for this transaction.
This is a user specific setting.
Now I can see that at the end of the screen explained above, there are certain fields that are not assigned.
Example, in FB70, the "Fld name" ACGL_ITEM-UZAWE is assigned to Pmt meth.supl. but ACGL_ITEM_GEN-GEN_CHAR1 is not assigned to anything.
I want to use this field ACGL_ITEM_GEN-GEN_CHAR1 for Reference Key 1.
Can anyone please guid me how to use this functionality of SAP?
Thanks in anticipation,
Nitish

Hi
I think the table in which it is updating the data has some constraint ....check the constraints

Custom Enjoy Transaction

How to create custom transaction like enjoy transaction where SAP uses Expand and collapse button to Expand and Collapse screen block.
Can any one have small sample program to do that?

Ok, Here is a sample program, copy and paste this code into a test program.
1) Create screen 100, assign OK_CODE as the ok code field.
2) Enter this code in the flow logic.
process before output.
module status_0100.
call subscreen subscreen_area1 including sy-repid the_subscreen.
process after input.
call subscreen subscreen_area1 .
module user_command_0100.
3) In screen 100, using the graphical layout editor, create a subscreen area and call it "subscreen_area1".
Add a pushbutton to this screen, and make sure to assign the function code as "PUSH".
4) Create screen 0110, make sure to specify that it is a subscreen in the attributes tab. Now begin putting some UI elements on the screen 0110. I just added a static text box, or label.
5) Create screen 0199, make sure to specify that it is a subscreen in the atttributes tab. Put nothing on this screen as it will be our DUMMY screen.
Here is the program code.
report zrich_0001.
data: ok_code type sy-ucomm.
data: save_ok type sy-ucomm.
data: the_subscreen type sy-dynnr value '0110'.
start-of-selection.
call screen 100.
*&      Module STATUS_0100 OUTPUT
module status_0100 output.
* SET PF-STATUS 'xxxxxxxx'.
* SET TITLEBAR 'xxx'.
endmodule.                    "status_0100 OUTPUT
*&      Module USER_COMMAND_0100 INPUT
module user_command_0100 input.
save_ok = ok_code.
case ok_code.
    when 'PUSH'.
      clear ok_code.
      if the_subscreen = '0110'.
        the_subscreen = '0199'.
      elseif the_subscreen = '0199'.
        the_subscreen = '0110'.
      endif.
endcase.
endmodule.                    "user_command_0100 INPUT
Now run the program. Notice that every time you press the pushbutton that the screen changes, it toggles back and forth between the screen 0110 and 0199.
Have fun.
Regards,
Rich Heilman

Screen Variant for ENjoy Transaction

Hi all,
I want to create screen variant for enjoy transaction, i.e fb60. Through the guide in another threads, I click on the square icon, above the scroll bar on the table control (used for entering document line items). When I create new variant, hide some columns and save this screen variant, everything is not changed. How to apply this screen variant to this transaction ?
I also use function "Add screen variant" when right click on this screen, but nothing changes.
Thank you very much for your helps.
Sylvecat.

That little button you mention (above the scroll bars) will not create screen variants for this transaction.
You have to use transaction SHD0 (also accessible by pressing Ctrl+F4 once you are inside FB60).
Search inside http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCDWBCEX/BCDWBCEX.pdf for the keywords SHD0 more info on usage, etc. if you need help with SHD0.
Please remember to assign points if found useful.
Regards,
Gulshan

List of SAP Enjoy Transactions

Does any one has the list of SAP Enjoy transactions.
please send me [email protected]
It is required immediately. Pls Help.

Hi
Tcode for MM Module
All transaction are stored in table TSTC.
Transaction for MM module start with M.
IH09 - Display Material
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material
ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.
ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs
ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MBRL - Return Delivery per Mat. Document
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB1B - Transfer Posting
MIBC - ABC Analysis for Cycle Counting
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI21 - Print physical inventory document
MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.
MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences
MI11 - Physical Inventory Document Recount
MI07 - Process List of Differences
MI37 - Batch Input: Post Differences
CT01 - Create Characteristic
CT02 - Change Characteristic
CT03 - Display Characteristic
CL01 - Create Class
CL02 - Classes
CL03 - Display Class
CL04 - Delete Class
CL2B - Class Types
Important SAP MM Tcodes 1
ME01                 Maintain Source List
ME03                 Display Source List
ME04                 Changes to Source List
ME05                 Generate Source List
ME06                 Analyze Source List
ME07                 Reorganize Source List
ME08                 Send Source List
ME0M                 Source List for Material
ME11                 Create Purchasing Info Record
ME12                 Change Purchasing Info Record
ME13                 Display Purchasing Info Record
ME14                 Changes to Purchasing Info Record
ME15                 Flag Purch. Info Rec. for Deletion
ME16                 Purchasing Info Recs. for Deletion
ME17                 Archive Info Records
ME18                 Send Purchasing Info Record
ME1A                 Archived Purchasing Info Records
ME1B                 Redetermine Info Record Price
ME1E                 Quotation Price History
ME1L                 Info Records Per Vendor
ME1M                 Info Records per Material
ME1P                 Purchase Order Price History
ME1W                 Info Records Per Material Group
ME1X                 Buyer's Negotiation Sheet for Vendor
ME1Y                 Buyer's Negotiat. Sheet for Material
ME21                 Create Purchase Order
ME21N                Create Purchase Order
ME22                 Change Purchase Order
ME22N                Change Purchase Order
ME23                 Display Purchase Order
ME23N                Display Purchase Order
ME24                 Maintain Purchase Order Supplement
ME25                 Create PO with Source Determination
ME26                 Display PO Supplement (IR)
ME27                 Create Stock Transport Order
ME28                 Release Purchase Order
ME29N                Release purchase order
ME2A                 Monitor Confirmations
ME2B                 POs by Requirement Tracking Number
ME2C                 Purchase Orders by Material Group
ME2J                 Purchase Orders for Project
ME2K                 Purch. Orders by Account Assignment
ME2L                 Purchase Orders by Vendor
ME2M                 Purchase Orders by Material
ME2N                 Purchase Orders by PO Number
ME2O                 SC Stock Monitoring (Vendor)
ME2S                 Services per Purchase Order
ME2V                 Goods Receipt Forecast
ME2W                 Purchase Orders for Supplying Plant
ME308                Send Contracts with Conditions
ME31                 Create Outline Agreement
ME31K                Create Contract
ME31L                Create Scheduling Agreement
ME32                 Change Outline Agreement
ME32K                Change Contract
ME32L                Change Scheduling Agreement
ME33                 Display Outline Agreement
ME33K                Display Contract
ME33L                Display Scheduling Agreement
ME34                 Maintain Outl. Agreement Supplement
ME34K                Maintain Contract Supplement
ME34L                Maintain Sched. Agreement Supplement
ME35                 Release Outline Agreement
ME35K                Release Contract
ME35L                Release Scheduling Agreement
ME36                 Display Agreement Supplement (IR)
ME37                 Create Transport Scheduling Agmt.
ME38                 Maintain Sched. Agreement Schedule
ME39                 Display Sched. Agmt. Schedule (TEST)
ME3A                 Transm. Release Documentation Record
ME3B                 Outl. Agreements per Requirement No.
ME3C                 Outline Agreements by Material Group
ME3J                 Outline Agreements per Project
ME3K                 Outl. Agreements by Acct. Assignment
ME3L                 Outline Agreements per Vendor
ME3M                 Outline Agreements by Material
ME3N                 Outline Agreements by Agreement No.
ME3P                 Recalculate Contract Price
ME3R                 Recalculate Sched. Agreement Price
ME3S                 Service List for Contract
ME41                 Create Request For Quotation
ME42                 Change Request For Quotation
ME43                 Display Request For Quotation
ME44                 Maintain RFQ Supplement
ME45                 Release RFQ
ME47                 Create Quotation
ME48                 Display Quotation
ME49                 Price Comparison List
ME4B                 RFQs by Requirement Tracking Number
ME4C                 RFQs by Material Group
ME4L                 RFQs by Vendor
ME4M                 RFQs by Material
ME4N                 RFQs by RFQ Number
ME4S                 RFQs by Collective Number
ME51                 Create Purchase Requisition
ME51N                Create Purchase Requisition
ME52                 Change Purchase Requisition
ME52N                Change Purchase Requisition
ME52NB               Buyer Approval: Purchase Requisition
ME53                 Display Purchase Requisition
ME53N                Display Purchase Requisition
ME54                 Release Purchase Requisition
ME54N                Release Purchase Requisition
ME55                 Collective Release of Purchase Reqs.
ME56                 Assign Source to Purch. Requisition
ME57                 Assign and Process Requisitions
ME58                 Ordering: Assigned Requisitions
ME59                 Automatic Generation of POs
ME59N                Automatic generation of POs
ME5A                 Purchase Requisitions: List Display
ME5F                 Release Reminder: Purch. Requisition
ME5J                 Purchase Requisitions for Project
ME5K                 Requisitions by Account Assignment
ME5R                 Archived Purchase Requisitions
ME5W                 Resubmission of Purch. Requisitions
ME61                 Maintain Vendor Evaluation
ME62                 Display Vendor Evaluation
ME63                 Evaluation of Automatic Subcriteria
ME64                 Evaluation Comparison
ME65                 Evaluation Lists
ME6A                 Changes to Vendor Evaluation
ME6B                 Display Vendor Evaln. for Material
ME6C                 Vendors Without Evaluation
ME6D                 Vendors Not Evaluated Since...
ME6E                 Evaluation Records Without Weighting
ME6F                 Print
ME6G                 Vendor Evaluation in the Background
ME6H                 Standard Analysis: Vendor Evaluation
ME6Z                 Transport Vendor Evaluation Tables
ME80                 Purchasing Reporting
ME80A                Purchasing Reporting: RFQs
ME80AN               General Analyses (A)
ME80F                Purchasing Reporting: POs
ME80FN               General Analyses (F)
ME80R                Purchasing Reporting: Outline Agmts.
ME80RN               General Analyses (L,K)
ME81                 Analysis of Order Values
ME81N                Analysis of Order Values
ME82                 Archived Purchasing Documents
ME84                 Generation of Sched. Agmt. Releases
ME84A                Individual Display of SA Release
ME85                 Renumber Schedule Lines
ME86                 Aggregate Schedule Lines
ME87                 Aggregate PO History
ME88                 Set Agr. ***. Qty./Reconcil. Date
ME91                 Purchasing Docs.: Urging/Reminding
ME91A                Urge Submission of Quotations
ME91E                Sch. Agmt. Schedules: Urging/Remind.
ME91F                Purchase Orders: Urging/Reminders
ME92                 Monitor Order Acknowledgment
ME92F                Monitor Order Acknowledgment
ME92K                Monitor Order Acknowledgment
ME92L                Monitor Order Acknowledgment
ME97                 Archive Purchase Requisitions
ME98                 Archive Purchasing Documents
ME99                 Messages from Purchase Orders
ME9A                 Message Output: RFQs
ME9E                 Message Output: Sch. Agmt. Schedules
ME9F                 Message Output: Purchase Orders
ME9K                 Message Output: Contracts
ME9L                 Message Output: Sched. Agreements
MEAN                 Delivery Addresses
MEB0                 Reversal of Settlement Runs
MEB1                 Create Reb. Arrangs. (Subseq. Sett.)
MEB2                 Change Reb. Arrangs. (Subseq. Sett.)
MEB3                 Displ. Reb. Arrangs. (Subseq. Sett.)
MEB4                 Settlement re Vendor Rebate Arrs.
MEB5                 List of Vendor Rebate Arrangements
MEB6                 Busn. Vol. Data, Vendor Rebate Arrs.
MEB7                 Extend Vendor Rebate Arrangements
MEB8                 Det. Statement, Vendor Rebate Arrs.
MEB9                 Stat. Statement, Vendor Rebate Arrs.
MEBA                 Comp. Suppl. BV, Vendor Rebate Arr.
MEBB                 Check Open Docs., Vendor Reb. Arrs.
MEBC                 Check Customizing: Subsequent Sett.
MEBE                 Workflow Sett. re Vendor Reb. Arrs.
MEBF                 Updating of External Busn. Volumes
MEBG                 Chg. Curr. (Euro), Vend. Reb. Arrs.
MEBH                 Generate Work Items (Man. Extension)
MEBI                 Message, Subs.Settlem. - Settlem.Run
MEBJ                 Recompile Income, Vendor Reb. Arrs.
MEBK                 Message., Subs. Settlem.- Arrangment
MEBM                 List of settlement runs for arrngmts
MEBR                 Archive Rebate Arrangements
MEBS                 Stmnt. Sett. Docs., Vend. Reb. Arrs.
MEBT                 Test Data: External Business Volumes
MEBV                 Extend Rebate Arrangements (Dialog)
MECCP_ME2K           For Requisition Account Assignment
MEDL                 Price Change: Contract
MEI1                 Automatic Purchasing Document Change
MEI2                 Automatic Document Change
MEI3                 Recompilation of Document Index
MEI4                 Compile Worklist for Document Index
MEI5                 Delete Worklist for Document Index
MEI6                 Delete purchasing document index
MEI7                 Change sales prices in purch. orders
MEI8                 Recomp. doc. index settlement req.
MEI9                 Recomp. doc. index vendor bill. doc.
MEIA                 New Structure Doc.Ind. Cust. Sett.
MEIS                 Data Selection: Arrivals
MEK1                 Create Conditions (Purchasing)
MEK2                 Change Conditions (Purchasing)
MEK3                 Display Conditions (Purchasing)
MEK31                Condition Maintenance: Change
MEK32                Condition Maintenance: Change
MEK33                Condition Maintenance: Change
MEK4                 Create Conditions (Purchasing)
MEKA                 Conditions: General Overview
MEKB                 Conditions by Contract
MEKC                 Conditions by Info Record
MEKD                 Conditions for Material Group
MEKE                 Conditions for Vendor
MEKF                 Conditions for Material Type
MEKG                 Conditions for Condition Group
MEKH                 Market Price
MEKI                 Conditions for Incoterms
MEKJ                 Conditions for Invoicing Party
MEKK                 Conditions for Vendor Sub-Range
MEKL                 Price Change: Scheduling Agreements
MEKLE                Currency Change: Sched. Agreements
MEKP                 Price Change: Info Records
MEKPE                Currency Change: Info Records
MEKR                 Price Change: Contracts
MEKRE                Currency Change: Contracts
MEKX                 Transport Condition Types Purchasing
MEKY                 Trnsp. Calc. Schema: Mkt. Pr. (Pur.)
MEKZ                 Trnsp. Calculation Schemas (Purch.)
MELB                 Purch. Transactions by Tracking No.
MEMASSIN             Mass-Changing of Purch. Info Records
MEMASSPO             Mass Change of Purchase Orders
MEMASSRQ             Mass-Changing of Purch. Requisitions
MENU_MIGRATION       Menu Migration into New Hierarchy
MEPA                 Order Price Simulation/Price Info
MEPB                 Price Info/Vendor Negotiations
MEPO                 Purchase Order
MEQ1                 Maintain Quota Arrangement
MEQ3                 Display Quota Arrangement
MEQ4                 Changes to Quota Arrangement
MEQ6                 Analyze Quota Arrangement
MEQ7                 Reorganize Quota Arrangement
MEQ8                 Monitor Quota Arrangements
MEQB                 Revise Quota Arrangement
MEQM                 Quota Arrangement for Material
MER4                 Settlement re Customer Rebate Arrs.
MER5                 List of Customer Rebate Arrangements
MER6                 Busn. Vols., Cust. Reb. Arrangements
MER7                 Extension of Cust. Reb. Arrangements
MER8                 Det. Statement: Cust. Rebate Arrs.
MER9                 Statement: Customer Reb. Arr. Stats.
MERA                 Comp. Suppl. BV, Cust. Rebate Arrs.
MERB                 Check re Open Docs. Cust. Reb. Arr.
MERE                 Workflow: Sett. Cust. Rebate Arrs.
MEREP_EX_REPLIC      SAP Mobile: Execute Replicator
MEREP_GROUP          SAP Mobile: Mobile Group
MEREP_LOG            SAP Mobile: Activity Log
MEREP_MIG            SAP Mobile: Migration
MEREP_MON            SAP Mobile: Mobile Monitor
MEREP_PD             SAP Mobile: Profile Dialog
MEREP_PURGE          SAP Mobile: Purge Tool
MEREP_SBUILDER       SAP Mobile: SyncBO Builder
MEREP_SCENGEN        SAP Mobile: SyncBO Generator
MERF                 Updating of External Busn. Volumes
MERG                 Change Curr. (Euro) Cust. Reb. Arrs.
MERH                 Generate Work Items (Man. Extension)
MERJ                 Recomp. of Income, Cust. Reb. Arrs.
MERS                 Stmnt. Sett. Docs. Cust. Reb. Arrs.
MEU0                 Assign User to User Group
MEU2                 Perform Busn. Volume Comp.: Rebate
MEU3                 Display Busn. Volume Comp.: Rebate
MEU4                 Display Busn. Volume Comp.: Rebate
MEU5                 Display Busn. Volume Comp.: Rebate
MEW0                 Procurement Transaction
MEW1                 Create Requirement Request
MEW10                Service Entry in Web
MEW2                 Status Display: Requirement Requests
MEW3                 Collective Release of Purchase Reqs.
MEW5                 Collective Release of Purchase Order
MEW6                 Assign Purchase Orders WEB
MEW7                 Release of Service Entry Sheets
MEW8                 Release of Service Entry Sheet
MEW9                 mew9
MEWP                 Web based PO
MEWS                 Service Entry (Component)
ME_SWP_ALERT         Display MRP Alerts (Web)
ME_SWP_CO            Display Purchasing Pricing (Web)
ME_SWP_IV            Display Settlement Status (Web)
ME_SWP_PDI           Display Purchase Document Info (Web)
ME_SWP_PH            Display Purchasing History (Web)
ME_SWP_SRI           Display Schedule Releases (Web)
ME_WIZARD            ME: Registration and Generation
<b>Please Awards Point if help full</b>Thanks
Pankaj Kumar

What is difference between enjoy transactions and Normal transactions

What is difference between enjoy transactions and Normal transactions
Ex:- ME22 & ME22N
What is difference between these two.

hi ,
the transaction code with 'N' are created with help of object concept.
In your case ME22 is obsolete one and ME22N is the tcode created with object concept.
pls Reward helpful points
Thanks
Siva

How to add help splitter in a screen ? (as Sap Enjoy transactions)

Hello,
I would like to create some screens like sap enjoy transactions (me53n, me21n, me22n ...) with the button "i" and the help in the left splitter.
I don't want to change standard help but I want to use the same idea for our specifics transactions.
The mains questions I have are where this help is store and how to manage it ?
So can you explain me the steps I need to follow to do this ?
Thanks in advance for your help.
Simon

Not sure if I get you correctly, but I think you need a button to be placed in custom container. Is that right?
For this SAP introduced [Dynamic Documents|http://help.sap.com/saphelp_nw70/helpdata/EN/10/246858055711d4a7410000e83dd863/frameset.htm] which could be embeded into container. They are easy to use and gives nice look and feel.
For adding the buttons please refer standard program DD_ADD_FORM_BUTTON . Also you can see other possibilites it provides (links, forms, pictures etc) . All programs DD* present that.
Regards
Marcin

Update LIKP table while saving the output type in VT02N transaction

Hi All,
I have a requirement where i have to update Delivery Priority(LPRIO) field in LIKP table while saving the output type in VT02N transaction. I am not able to use the BAPI "BAPI_OUTB_DELIVERY_CHANGE" or FM "WS_DELIVERY_UPDATE" because, when we save the output type the programs that are configured in NACE are triggered in update mode and hence i will get a roll back error.
Let me know other ways of updating the table at the time of saving output type for shipment transaction VT02N.

This could be a result of one of the following reasons:
1: Incorrect smart form/routine assigned in the output configuration (NACE)
2: Serial number range of the delivery expired
3: The default settings of the user (SU01) processing the delivery is missing the default printer name.
Hope this is helpful
Manish

Urgent--==creation of object type in MASSOBJ transaction

hi all:
Could any one urgently tell me how to create object type in Massobj transaction.(this is done to delete purchase requisition in bulk in transaction 'Mass' (AND not in 'MASSOBJ').)
i have created in Massobj transaction by pressing 'new enteries' button, but several elements are missing.
so it give short dump after running transaction Mass.
Object type is created in Massobj transaction and executed in Mass transaction.
could anyone find solution for this urgetly.
thanx in advance
regards
raj

Hi,
There is an standard object BUS2105 to for the mass maintanance purpose.
You can directly go to MASS transaction and give the object type BUS2105 at the intial selection screen and don't mention any variant name.Execute it and displays the next screeen whereas you have the option to select the field you want and execute it again.Go to the next screen and specify the PR number range and specify the new value for the mass maintanace.After that you got to select the push button 'Carry out a mass change'.
I hope this would help you.
Thank you.
Regards,
karun.M

Hide a type of file System wide not just the extension*

Is it Possible & if So Howto hide a type of file System wide not just the extension*
Am trying to HIDE the Associated file for Photo Processing software in Finder, its a Specific file to the Program & holds the Raw data text Processed Info
. Would mean I would need to change each File individually
Is there a way/apple script?
Knowledge or experience would be Appreciated
Thanks

I followed these instructions and they work, but I also get errors. Here are two files in the directire, and the contents of ~/.profile, I called the function killextension:
I run the command to hide the PDF:
Note the two errors. Thank you very much, BTW. No more Dropbox attributes files!

Creating a query that provides a default transaction type for those transactions not categorized?

How could I create a query that provides a default transaction type for those transactions not categorized?
So assuming I have:
* Transactions table (with transactions)
* Categories table
* transactions_categories table - allows to allocate multiple categories (with a percentage)
- tranactionID
- categoryID
- percentageAllocation
* Usage is such that only non-personal categories have been applied through out data. So there is a lot of transactions with no categories applied
Aim:
* Want to create a query that creates a list of all the allocated amounts, so would include as columns: transaction.tDate, transaction.tTitle, categories.name, allocatedAmount(calculated from percentage * transaction amount)
BUT:
* How could I include in the query, the entries that cover all transaction that haven't been allocated, to a default category "personal", where the allocated Amount would be 100% of the transaction value
* And also (if it were possible), for transactions that have been categorized but not for the complete transaction value (say only 50% was allocated to a category), how to to cover this off to.

To default the value of the category:
select IIf(IsNull(Category),"Personal",Category) as Category,IIf(IsNull(Category),"100%",PercentageAllocation
) as PercentageAllocation from [yourtable]
What do you want to put the values of these ones:
And also (if it were possible), for transactions that have been categorized but not for the complete transaction
value (say only 50% was allocated to a category), how to to cover this off to.
Fouad Roumieh

Cannot select the newly created Screen variant in ENJOY transactions.

Hello All,
I have created a screen variant for a specific requirement from the client in transaction SHD0.
However I am unable to select this new screen variant in all ENJOY transactions.
When I try to select the screen variant in FB50-Post GL through>EDIT>Screen Variant, Select,Reset and Create Screen variants are greyyed out.
I have checked the setting in SU3, as well as FB00 for the Parameters, it appears to be correct.
Kindly help at the earliest!!
Regards
Shrutika

Hi,
Shrutika.
Try this I hope this may help you.
Go to FB50 at above left hand side will see Tree On option button. Click on that you will see Screen vairants for items option with drop down object. Simply click on that now select your desired screen variant by double clicking applied.
I hope this may help you to solve your issue. If you have any doubts feel free to ask.
Regards,
Pankaj A Bhalerao.

Hiii friends! how attached output type to a transaction

Hi gurus!
how to attached output type to a transaction.
for eg - i have created a outout type zexpt and i have to assigned to transaction VF01.
Regards,
Rahul

Hi
goto VF02 tcode
fro Menu
GOTO HEADER -> Output
define there
Output is a link between the Driver Program and the Sapscript,
An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
Check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
ex-how to config output type.
You will assign output types using Transaction NACE.
Do the follow steps to assign output type
1)Select Application Type V2 which will have description Shipping.
2)Click on Output types button.
3)Go to change mode by pressing Ctrl+F4.
4)Select one output type which already exists
5)Do Copy As(F6)
6)Give your output type against Output Type field.
7)Under General data Tab, Give Program and Form routine and Save the data.
i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
Check the following documentation
In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
If suppose data can be read from EDI then we should go for condition records.
So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
Go to the Transaction NACE.
choose the related sub module.. like billing or shipping
doubel click on Output Types
Choose the Output Type for which whcih you wanted your script to trigger
Then select the Output Type and double click on Processing Routine
Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
Device Types for SAP Output Devices (Detail Information)
Definition
The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
How do I choose the correct device type?
In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
These standard device types are completely defined and need no modification or extension before you use them in device definitions.
You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
Attributes of a Device Type
A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
Regards
Anji

Hide PO-Type in Enjoy-Transaction

Similar Messages

Maybe you are looking for