Correspondance variant

Hello All,
When I request the correspondance with particular variant, I am getting message like variant aaa of program xxxx is not the current version message number is DB 634. Can anyone please let me know how to adjust this variant.
Thank you
Srinivas

issue is solved

Similar Messages

User specific default variant setting

Hi gurus,
My requirement is Report should get executed with default user specific Variant.
For example while running MB51 system should pick the corresponding variant based on the user who is executing the report.
Based on threads i created variants with U_userid like U_RAM & U_LAX.
I checked with user ids of RAM and LAX, But system is not picking automatically.
can u help me

hi,
see this.
https://forums.sdn.sap.com/click.jspa?searchID=14929390&messageID=5872211

TC F110 - Protect the variant for the Print out/ data medium - RFFOIT_FOR

Hi Experts,
I have to protect the field "filename" in the program RFFOIT_FOR and I have to permit to user, when he runs the TC F110, to change only some field in the variant for the same program.
Can you help me?
Thanks in advance.
Best Regards
Giampaolo
Edited by: Giampaolo 76 on Oct 7, 2011 10:58 AM

Dear Giampaolo,
I did a test and if I try to change the variant using anothe user, I will get:
No authorization to change variant MAO2
    Message no. DB278
Diagnosis
    You tried to change a protected variant. This can only be done by the
    variant's creator.
System Response
    A protected variant can only be changed by its creator.
Procedure
    Contact the creator of the variant or create a corresponding variant
    yourself (for example by copying the protected variant).
Therefore if You switch on the flag "protect variant" into the Variant attributes, You could reach Your goal.
Mauri

What is t-code SHD0's 'Variant Groups' used for?

hi all:
What is t-code SHD0's 'Variant Groups' used for?
It seems can't work,who can help me?
thanksss.

Variant groups
An extension of the standard variants is involved in the variant groups; the standard groups are often insufficient:
Different users (groups) should work with different variants;
Some users should be able to execute a transaction with different variants.
This is possible - in addition to the advantages that the standard variants offer - with variant groups:
Variants from variant groups are automatically applied, but only for users that are assigned to them.
A user can be assigned to several groups and can change the assignment.
The values of the groups are not applied in the batch input mode.
If a transaction is started with another transaction variant, the values are not additionally applied to a variant group.
How are the variant groups maintained?
You can enter the group names on the "Variant Group" tab and maintain variant groups with the "Create" or "Change" functions.
The group name must be in the "correct" namespace.
In addition, there are two Where-Used Lists:
Which users are assigned to the group,
For which transactions the group applies.
Which transaction variants belong to the groups?
The name of a transaction variant that is to belong to a group meets the following naming conventions:
<Name of variant group><name of transaction code>. Example: A transaction variant is to be created for the XYZ transaction that belongs to GROUP1. The name of the transaction variant is then GROUP1XYZ.
Due to this naming convention, the group name must be in the "correct" namespace.
Transaction variants that (randomly) meet this naming convention do not necessarily belong to a group. The group assignment is activated by
1. Creating a group
2. Assigning users to this group
A transaction variant that belongs to a group can also be used this way, like a transaction variant without a group.
How are the transaction variants that belong to a group maintained?
Transaction variants that belong to a group are maintained in the same way as all other transaction variants, they are distinguished using a naming convention (<name of variant group> <name of transaction codes>).
They can be maintained in the "transaction variants" tab or in the "variant groups" tab. If you maintain them in the "variant groups" tab, you must always enter the transaction code so that the name of the transaction variant can be determined.
Under what conditions is a variant from a group applied?
A variant from a group is applied if users are assigned.
(Only for the assigned users, all other users get the original transaction with a variant from a different group.)
It is NOT sufficient to
Create a group
Create a variant that satisfies the naming convention.
How do you assign users to groups?
You can assign users in the "variant groups" tab in the "user assignment".
Enter the user name.
The user is assigned to the group with the "assign" function, but they see original transaction(s) or the transactions with variants from another group as the proposal.
The assignment of users to the group is deleted using the "delete assignment" function.
The user is assigned to the group using the "Set Proposal" function and the relevant transactions are started for this user with the corresponding variants.
The proposal is canceled with the "Cancel Proposal" function, the assignment itself remains.
If you enter the user names generically (*), you receive a selection screen in which you can
Choose whether assignments or proposals are to be changed
Further restrict user names (the group in the "all users from group" option has nothing to do with the variant group, it concerns the "user group for authorization check" from the user master record (logon data)).
By choosing "Execute", you receive a list in which you can further restrict the user selection. The "Save" function saves the assignments for all selected users.
If you want to start the report in the background, you can choose if just the list should be outputted, or if the database changes should also be performed.
If a user is additionally also to be able to execute the original transaction, he must be assigned to the "empty group", the allocation takes place in the same way, in this case, nothing is simply entered in the group name field.
Regards,
Joy.

Transaction variant misunderstood. I will reward points !!!!!

Hello Gurus, i am trying, for some time now, to create a transaction variant. The goal is to set a field read-only in the "ea13" transaction.
When is use "se93" to create a transaction variant i have to fill in the transaction variant name, but when i do that it says that the transaction variat does not exist, confusing because i want to create a new transaction variant.
When i use "shd0" and fill in the name of my new transaction variant and click create i don`t have any fields, everything is empty. Can anyone give me an exact example or something. I found on the forum a link to a step by step how to, but it didn`t work.
Im working on R/3 Release 4.6C.
Please help, i will reward lots of points !!!

Hi,
Starting Transaction Variants
A transaction can be started with a variant:
Using the Test function from the maintenance transaction
By a program that includes a call to function module RS_HDSYS_CALL_TC_VARIANT
Function module RS_HDSYS_GET_TC_VARIANT checks to see if a transaction variant is active and returns its name and (if possible) its current values (screen variants, inactive functions).
Using its own transaction code as a variant transaction.
When a transaction with variant is called using the Test function, for technical reasons it is started in call mode. Some transactions behave differently in call mode than when called directly.
A variant transaction is started either in call mode or LEAVE TO TRANSACTION, depending to how it is called.
If you call a transaction with variant from a program using the function module RS_HDSYS_CALL_TC_VARIANT, you can use the function module to determine which mode is called (call mode or LEAVE TO TRANSACTION).
Variant Transactions
A transaction with a variant can have its own transaction code, which you can then use to execute the transaction with the appropriate variant.
To create a variant transaction, proceed as follows:
Choose Goto ® Create vari. trans. from the initial transaction variant maintenance screen.
Enter a transaction name and corresponding short text. Transaction type Variant transaction is already set. The following screen already contains default values for the name of the calling transaction, the variant name, and the client-specific or cross-client variant checkbox.
Save your entries.
Example:
Variant ABC has been defined for transaction Z000. We now want to create the variant transaction ZVAR.
Name of the new transaction: ZVAR
Name of the calling transaction: Z000
Name of the variant: ABC
Transaction ZVAR starts transaction Z000 with variant ABC.
If the variant specified for a variant transaction does not exist (in the current client), then the calling transaction will be started without variant.
The Standard Transaction Variant
Standard transaction variants have a special purpose. You can use any transaction variant as a standard variant. Use the Activate and Deactivate functions to use a specific transaction variant as a standard variant or to deactivate it.
If a standard variant is active for a transaction, the system searches for the variant automatically whenever the transaction is started and adopts its values.
If a transaction with an active standard variant is started with another variant, the values of the standard variant are not imported.
If a transaction with an active standard variant is started in batch input mode, the values of the standard variant are not imported either.
Variant Transactions and Parameter Transactions
Variant transactions can be client-specific (this means that their corresponding variants can also be client-specific).
In a variant transaction, several screens can be given pre-assigned values or suppressed. In a parameter transaction this can only be done for the initial screen.
You can suppress as many screens as you like in variant transactions; in parameter transactions you can only suppress the initial screen. If a screen is suppressed in a variant transaction, it is never displayed. An initial screen that has been suppressed in a parameter transaction is only not displayed when the transaction is initially called.
You can use the function Change transaction type during transaction code maintenance to convert a parameter transaction to a variant transaction. The system creates a transaction variant and a screen variant for its initial screen containing the values of the parameter transaction. The system suggests the name CV_P_ for these variants. The default name may be changed. The variant is created for the called transaction. It can be changed in Transaction Variant Maintenance and Screen Variant Maintenance. The transaction variant can be created in the current client or as a cross-client variant.

Language of Catalog Variant

Requirement: Create variant based on the sales organisation. When the
user will access B2B then he could see the product catalog text in
local language.
Current set up:
We are using B2B web shop in our project. We have created product
catalog 'SPM Direct' with catalog type : Both. We have created catalog
variants for 3 sales area ( the details are attached). We are facing
following issue:
We have created variant for German sales organisation with
language 'German' and also maintained all the text in German language.
same way we have created for French and UK sales organisation.
After the replication of the catalog on web shop we found that the text
appearing in the catalog only in 'German' language. (as first variant
is German) . when we change the first variant language to English then
all the text will change to English.
So would like to know any setting regarding the variant language ?

Nilesh,
Constraint with ISA B2B or B2C webshops is that you can not have multiple variants for the same shop.
Hence if you have three different variants maintained for DE,EN,FR you need to create three different web shops and assign the variants to them respectively.
Since variants correspond to a sales area, all your Sold To's maintained for a particular sales area will see all the shops maintained with the variant for that sales area.
For eg.
Suppose BP A is maintained for Sales Org 1000,10 and 1000,20.
You have maintained 2 variants in your catalog
Variant 1 -> language DE sales Org 1000, 10
Variant 2 -> language EN sales Org 1000, 20
Now you will have to create two web shops
Shop1 with varaint 1
Shop2 with variant 2
When BP A's contact person B logs on to the B2B site he will see two shops Shop1 and Shop2 and will have to select one of them for viewing the catalog and corresponding variant.
If he selects Shop1 he will see language De
If he selects Shop2 he will see language EN
Hope this helps.
Thx,
Bharat.

CRM 7.0: set up IPC product configuration

Dear experts,
we set up a CRM 7.0 with ERP 6.0 backend integration. In the ERP we apply ERP variant configuration (Materials). Quite simple: some configurable materials (material type KMAT) with a few characteristics and product variants of them (material type FERT) which are maintained in order processing. Variant conditions are maintained and automatically determined for product items. Now we need this in CRM for opportunity processing.
Therefore we have created Knowledge Base and Runtime Version for the configurable products in ERP and downloaded test materials (one KMAT and one FERT (product variant) into CRM (download objects MATERIAL and SCE). In CRM product master data maintenance for the KMATconfigurable tab with the configuration profile is displayed. Afterwards we downloaded condition master data into CRM, among others variant condition VA00 with condition table A057. Everything looks fine.
In CRM we want to set up opportunity management. In the opprotunity transaction processing pricing is working already besides the determination of variant pricing. As we intend to maintain only FERT materials (product variants)we do not need interactive product configuration in CRM sales order or product simulation in CRM product master data. We only want the variant prices to be determined automatically for the product variants (FERT) in opportunity processing. That is why we are not sure if it necessary to set IPC configuration settings (XCM etc.). This is my first question. Nevertheless we started to maintain settings for product configuration in order to find out if this is solves our problem:
1.) XCM configuration (IPC): we set up a customer application for "crmproductsimulation" and defined customer components jco (RFC test worked) and productvariants and restarted J2EE Instance in TX: SMICM
2.) We set up product configuration customizing:
table: COMM_IPC_PROP: caller; crmproductsimulation; scenario.xcm; ZCRMproductssimulation
table: COMM_IPC_URL: UI_CFG; http://<host>:<port>100/ipc/ipc/command.do
When starting simulation of product model for configurable product in TX: COMMPR01 I get following error message: "HTTP500: ISA Framework: The [XCM application configuration]='ZCRMproductssimulation' does not exist. Check XCM configuration.
Details:   No details available". This application is maintained in XCM so I assume something else is missing.
To sum up my questions:
1.) Is it necessary to set up IPC product configuration as described above when we only want to maintain FERT products which are product variants and determine corresponding variant prices (VA00). No interactive product configuration is necessary.
2.) If it is necessary to set up IPC product configuration to active product configuration (to see product variants in product master data maintenance and opportunity processing and corresponding variant condition data), what did I do wrong?
Thank you very much for your help.
KInd regards,
Mark

Hi Arup,
thank you very much for your reply.
Concerning XCM / CRM customizing I have done the steps you recommended:
1. XCM: I created customer applications for crmordermaintain and crmproductsimulation and maintained customer component JCO for both of them (Assigned JCO User has SAPALL / SAPNEW, test run was successful) Active and default are ticked. Are there any further steps missing.May be in General Application Settings > Customer > ipcwebappconfig - I changed nothing there (SSLenabled: true)
2. In CRM customizing I maintained tables as follows:
COMM_IPC_PROP:
caller   crmordermaintain scenario.xcm   Zcrmordermaintain (name of customer xcm app -case sensitive)
caller   crmproductsimulation scenario.xcm Zcrmproductsimulation (name of customer xcm app -case sensitive)
COMM_IPC_URL:
Destination: UI_CFG ;Appl. <blank>; URL: http://<host>:<J2EEport/ipc/ipc/command.do
Calling the IPC product configuration e.g. from the CRM product master (simulate model), I get the already mentioned HTTP error:"ISA Framework: The [XCM application configuration]='Zcrmproductsimulation' does not exist. Check XCM configuration.".
That's why I am thinking that something is missing concerning the communication between CRM application and IPC,because XCM applications do definitely exist.
Is the URL correct .../ipc/ipc/commando.do which I maintained in table COMM_IPC_URL?
Is it possible to check if communication between CRM Online and Java does work respectively what do you exactly mean by "IPC URL must be available for UI_CFG"? UI_CFG ist a RFC-connection which has to be maintained additionaly and if so what has to be maintained exactly?
You mentioned a RFC_USER (This is the JCO-User I suppose?)and J2ee user. Is the J2ee user just the admin user of the J2EE engine or do you mean something different?
Thanks in advance for your further help.
Best regards,
Mark
Edited by: Mark Willhoeft on Jun 4, 2010 8:36 PM
Just one further thing: After changing XCM config I restarted J2EE by TX SMICM (Administration - J2EE Instance local - Send soft shutdown - with restart). Is this enough to restart J2EE and activate changed XCM settings or has the restart to be handled different?

How to change the header of Material BOM in a program for alternative BOM ?

Requirement: An Inbound IDOC creates /change/delete Alternative Material BOM. The Alternative Material BOM can have alternative values from 1 to 99.
ISSUE: I am good with CREATE and DELETE BOM. The issue is with CHANGE of header Material BOM. The fields which we need to change in the header is the base quantity, BOM status, Lot Size from and Lot Size to. Please note that I am able to change the item details of the BOM with FM CSAI_BOM_MAINTAIN. I find no FM /BAPI which would change the header of a material BOM.
Please NOTE that I am using BAPI_MATERIAL_BOM_GROUP_CREATE to create alternative Material BOM. This has a parameter in TABLES called "VARIANTS" which has a field CS_FUNCTION which can have value from NEW/CHG/DEL .Also ,there is another parameter in TABLES called "ITEMASSIGNMENTS" which has a field CS_FUNCTION which can have value from NEW/CHG/DEL which implies this FM will allow us to change the BOM. But this does not work when I use it for CHANGE scenario with CHG value. I debugged this BAPI and observed it requires a STNLR(Bill of Material) value . This field is not there in any of the structure. I am not sure if I am passing the right parameters to it.
Let me know if the parameters are passed correctly for CHANGE scenario.
Also let me know if there is any other way(FM/BAPI) to update the Header of the Material BOM ?
Here is the code I am using:
*& Report ZTEST_S_E
REPORT ZTEST_S_E.
* This code will create a material BoM for the material
* MAINMATERIAL with the components COMPON1 and COMPON2.
* Data Declaration
DATA:
it_bomgroup LIKE bapi1080_bgr_c OCCURS 0 WITH HEADER LINE,
it_variants LIKE bapi1080_bom_c OCCURS 0 WITH HEADER LINE,
it_items LIKE bapi1080_itm_c OCCURS 0 WITH HEADER LINE,
it_matrel LIKE bapi1080_mbm_c OCCURS 0 WITH HEADER LINE,
it_itemas LIKE bapi1080_rel_itm_bom_c OCCURS 0 WITH HEADER LINE,
it_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
* Fill the data
* Material BoM Group Header Data
CLEAR it_bomgroup.
it_bomgroup-bom_group_identification = 'BAPI_SMP_COL1'.
it_bomgroup-object_type = 'BOM'.
it_bomgroup-object_id = 'SIMPLE1'.
it_bomgroup-bom_usage = '1'. " YOU COULD CHANGE THE BOM USAGE TO YOUR
*NEEDS
it_bomgroup-ltxt_lang = sy-langu.
it_bomgroup-technical_type = ' '.
it_bomgroup-bom_text = 'Simple BoM - FM'.
APPEND it_bomgroup.
* Header Details of the different variants
CLEAR it_variants.
it_variants-CHANGE_NO = '500000000349'.
it_variants-bom_group_identification = 'BAPI_SMP_COL1'.
it_variants-object_type = 'BOM'.
it_variants-object_id = 'SIMPLE1'.
it_variants-alternative_bom = '01'.
it_variants-bom_status = '01'.
it_variants-base_qty = '2.000'.
it_variants-valid_from_date = sy-datum.
it_variants-function = 'CHG'.
APPEND it_variants.
* Details of the items of the variants
CLEAR it_items.
it_items-bom_group_identification = 'BAPI_SMP_COL1'.
it_items-object_type = 'ITM'.
it_items-object_id = 'SIMPLE1'.
it_items-item_no = '0010'.
it_items-item_cat = 'L'.
it_items-component = '030790490'.
it_items-comp_qty = '2'.
it_items-valid_from_date = sy-datum.
APPEND it_items.
CLEAR it_items.
it_items-bom_group_identification = 'BAPI_SMP_COL1'.
it_items-object_type = 'ITM'.
it_items-object_id = 'SIMPLE1'.
it_itemas-change_no = '500000000138'.
it_items-item_no = '0020'.
it_items-item_cat = 'L'.
it_items-component = '030790490'.
it_items-comp_qty = '3'.
it_items-valid_from_date = sy-datum.
APPEND it_items.
* Details of the materials of the different variants
CLEAR it_matrel.
it_matrel-bom_group_identification = 'BAPI_SMP_COL1'.
it_matrel-material = '030790490'.
it_matrel-bom_usage = '1'.
it_matrel-alternative_bom = '01'.
APPEND it_matrel.
* Linking items to the corresponding variants
CLEAR it_itemas.
it_itemas-bom_group_identification = 'BAPI_SMP_COL1'.
it_itemas-sub_object_type = 'ITM'.
it_itemas-sub_object_id = 'SIMPLE1'.
it_itemas-super_object_type = 'BOM'.
it_itemas-super_object_id = 'SIMPLE1'.
it_itemas-valid_from_date = sy-datum.
it_itemas-function = 'CHG'.
APPEND it_itemas.
* Create variants
CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'
EXPORTING
all_error = 'X'
TABLES
bomgroup = it_bomgroup
variants = it_variants
items = it_items
materialrelations = it_matrel
itemassignments = it_itemas
return = it_return.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
LOOP AT it_return.
WRITE:/ it_return-type, it_return-id, it_return-number,
it_return-message.
ENDLOOP.
Let me know if the parameters are passed correctly for CHANGE scenario.
Also let me know if there is any other way(FM/BAPI) to update the Header of the Material BOM ?

Try doing something like this:
class MyJTextArea extends JTextArea {
    public boolean keyDown(Event evt,int key) {
        if(key == 13 || key == 10) { // or whatever ascii codes enter may have
            // move carret to next line
        } else {
            super.keyDown(evt, key);
}which means you have got to catch the enter-key before the actutal JTextArea does this.
p.s. look at my post, maybe you can help me, too.
http://forum.java.sun.com/thread.jsp?forum=5&thread=465803&tstart=0&trange=100

Can not open newly created internet sales shop

Hello,
Technical Landscape and Software components:
EP   640 SP 9
J2ee 640 SP 9
ISA 40 SP 10
CRM 40 SP 10
TREX 6.1.09
We use the b2b szenario in combination with CRM(not R/3)
we have the following problems:
1.
- We have created a new Product catalog with the webcatadmin tool
- afterward we have replicated the complete product catalog(no errors)
- we do not use any ipc at the moment
- we have created a new b2b internet shop and added the product catalog and the corresponding variant to the shop(szenario b2b)
- if we now go to the login page of the b2b loginpage(http://ntsrv854.merz.de:50000/b2b/b2b/init.do) and enter the user and password the following message appears:
    "A serious system error has occurred Contact the administrator:
     The shoplist read from buffer is empty Log on"
- so we decided to enter the created shop directly(http://ntsrv854.merz.de:50000/b2b/b2b/init.do?shop=MDB2R) and now the
    following errors appear:
    "An error occured while shop MDB2R was loaded.
     An error occured while shop MDB2R was loaded."
    The trace file default.trace of the portal displays the following
    message:
#1.5#0015600C761000610000036A000033D4000413FEE7BC5467#1147885437344#bbcom.sapmarkets.isa.isacore.action.ShopShowListAction#sap.com/crm.b2b#bbcom.sapmarkets.isa.isacore.action.ShopShowListAction#Guest#18##NTSRV854_E6S_8383950#Guest#20ce6220e5c711daafa80015600c7610#SAPEngine_Application_Thread[impl:3]_31##0#0#Error#1#/#Plain###[(J2EE8383900)ID8383950DB11285026301441142212End|exception.panic] Panic
com.sapmarkets.isa.core.PanicException: panic.shoplist.zeroelements
     at com.sapmarkets.isa.isacore.action.ShopShowListAction.isaPerform(ShopShowListAction.java:277)
     at com.sapmarkets.isa.isacore.action.IsaCoreBaseAction.isaPerform(IsaCoreBaseAction.java:568)
     at com.sapmarkets.isa.isacore.action.IsaCoreBaseAction.isaPerform(IsaCoreBaseAction.java:608)
     at com.sapmarkets.isa.isacore.action.IsaCoreBaseAction.doPerform(IsaCoreBaseAction.java:489)
     at com.sapmarkets.isa.core.BaseAction.perform(BaseAction.java:197)
     at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)
     at com.sapmarkets.isa.core.ActionServlet.process(ActionServlet.java:430)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:509)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:290)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:346)
     at org.apache.struts.action.ActionServlet.processActionForward(ActionServlet.java:1758)
     at com.sapmarkets.isa.core.ActionServlet.processActionForward(ActionServlet.java:267)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1595)
     at com.sapmarkets.isa.core.ActionServlet.process(ActionServlet.java:430)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:509)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:290)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:346)
     at org.apache.struts.action.ActionServlet.processActionForward(ActionServlet.java:1758)
     at com.sapmarkets.isa.core.ActionServlet.processActionForward(ActionServlet.java:267)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1595)
     at com.sapmarkets.isa.core.ActionServlet.process(ActionServlet.java:430)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:509)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.sapmarkets.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:71)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:368)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Info: The User is maintained as an internet user and has the following roles:
SAP_CRM_INTERNET_CUSTOMER
SAP_CRM_INTERNET_SELF_SERVICE
SAP_CRM_ISA_UA_SUPERUSER
SAP_CRM_ISA_WEBSHOP_MANAGER
The user is assigned to the organizational unit which is assigned in the variant of the product catalog! The Relationship to an sold to and contact person also exists.
What should be the problem?
Best regards
Carmen Kosack

Did you ever figure this out? I just got a new iPhone and am having the same problem.

BOM Cretion error with BAPI : BAPI_MATERIAL_BOM_GROUP_CREATE

Dear All,
Desc:
Here i am trying to create a BOM with differnet componants :
i am getting the below error while creating the BOM in varient alternative..
W BAPI1080             028
Error/warning when checking the structure of the BOM group with ID=BOMGROUP1
A BAPI1080             010
Variant/alternative 01 can only occur once with the function NEW
A BAPI1080             010
Variant/alternative 01 can only occur once with the function NEW
A BAPI1080             010
Variant/alternative 01 can only occur once with the function NEW
Please find the below code:
Code:
To get SC details
Get Plant details
SELECT * FROM y27d_dc_marc
       INTO TABLE l_t_y27d_dc_marc
      WHERE instnr = '552'.                                 "instnr
IF sy-subrc = 0.
SORT l_t_y27d_dc_marc BY werks.
ENDIF.
IF l_t_y27d_dc_marc IS NOT INITIAL.
Get all Regions
SELECT * FROM y27d_dc_dt_plant
         INTO TABLE l_t_y27d_dc_dt_plant
         FOR ALL ENTRIES IN l_t_y27d_dc_marc
         WHERE werks = l_t_y27d_dc_marc-werks.
ENDIF.
Read the SC Details
READ TABLE l_t_y27d_dc_dt_plant
           INTO l_r_y27d_dc_dt_plant
     WITH KEY werks_typ = g_c_sc.                           "SC
IF sy-subrc = 0.
Populate SC details
g_f_sc_plant = l_r_y27d_dc_dt_plant-werks.
ENDIF.
Material BoM Group Header Data
l_r_bomgroup-bom_group_identification = 'BOMGROUP1'.
l_r_bomgroup-object_type              = 'BGR'.
l_r_bomgroup-object_id                = 'BOMGROUP1'.
l_r_bomgroup-bom_usage                = '1'. " YOU COULD CHANGE THE BOM USAGE TO YOUR needs
Plant assignment for the corresponding group
l_r_bomgroup-created_in_plant         = g_f_sc_plant.       "'0470'.
l_r_bomgroup-ltxt_lang                = sy-langu.
l_r_bomgroup-technical_type           = 'M'.                     " bomgroup-technical_type           = wstzu-stlty.
l_r_bomgroup-bom_text                 = 'Test for BOM YSPR'.
APPEND l_r_bomgroup TO l_t_bomgroup.
CLEAR l_r_bomgroup.
DATA : l_f_var_alter TYPE stalt,
       l_f_var_alter_cnt TYPE stalt.
Get BOM Item details
SELECT * FROM y27d_dc_bom
         INTO TABLE l_t_bom_item
         WHERE instnr = '552'.
IF sy-subrc = 0.
DESCRIBE TABLE l_t_bom_item LINES l_f_var_alter.
Populate item data
LOOP AT l_t_bom_item INTO l_r_bom_item.
Varient alternative for all the corresponding componants
    l_f_var_alter = sy-tabix.
Details of the items of the variants
    l_r_itemdata-bom_group_identification    = 'BOMGROUP1'.
    l_r_itemdata-object_type                 = 'ITM'.
    l_r_itemdata-object_id                   = l_r_bom_item-bcomponant. "'MDTRAW2011'
    l_r_itemdata-item_no                     = l_r_bom_item-bitemno."'0010'.
    l_r_itemdata-item_cat                    = l_r_bom_item-bitemcat.    "'L'.
    l_r_itemdata-component                   = l_r_bom_item-bcomponant. "'MDTRAW2011'.
    l_r_itemdata-comp_qty                    = l_r_bom_item-bquan."'2'.
    l_r_itemdata-valid_from_date             = sy-datum.
    APPEND l_r_itemdata TO l_t_itemdata.
    CLEAR l_r_itemdata.
Item componant assignment to a variant/alternative
    l_r_variants-bom_group_identification = 'BOMGROUP1'.
    l_r_variants-object_type              = 'BOM'.
    l_r_variants-object_id                = l_r_bom_item-bcomponant. "'MDTRAW2011'.   "'BOM1'.
    l_r_variants-alternative_bom          = '01'.
    l_r_variants-bom_status               = '01'.
    l_r_variants-base_qty                 = '100'.
    l_r_variants-valid_from_date          = sy-datum.
    l_r_variants-function                 = 'NEW'.
    APPEND l_r_variants TO l_t_variants.
    CLEAR l_r_variants.
Item componant assignment to linked items
Linking items to the corresponding variants
    l_r_itemlink_to_var-bom_group_identification = 'BOMGROUP1'.
    l_r_itemlink_to_var-sub_object_type          = 'ITM'.
    l_r_itemlink_to_var-sub_object_id            = l_r_bom_item-bcomponant.       "'MDTRAW2011'.       "componant linked with varient
    l_r_itemlink_to_var-super_object_type        = 'BOM'.
    l_r_itemlink_to_var-super_object_id          = l_r_bom_item-bcomponant.       "'MDTRAW2011'.       "componant linked with varient
    l_r_itemlink_to_var-valid_from_date          = sy-datum.
    l_r_itemlink_to_var-function                 = 'NEW'.
    APPEND l_r_itemlink_to_var TO l_t_itemlink_to_var.
    CLEAR l_r_itemlink_to_var.
ENDLOOP.
ENDIF.
Get the Header details
SELECT SINGLE * FROM y27d_dc_mara
                INTO l_r_bom_head_mara
                WHERE instnr = '552'.               "instnr
IF sy-subrc = 0.
Populate header data
l_r_bom_head-bom_group_identification = 'BOMGROUP1'.
l_r_bom_head-material                 = l_r_bom_head_mara-matnr. "'MDT01022011'.
l_r_bom_head-plant                    = g_f_sc_plant.     "'0470'.
l_r_bom_head-bom_usage                = '1'.              "'5'.
l_r_bom_head-alternative_bom          = '01'.
APPEND l_r_bom_head TO l_t_bom_head.
CLEAR l_r_bom_head.
ENDIF.
Create BOM
CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'
EXPORTING
    all_error         = 'X'
TABLES
    bomgroup          = l_t_bomgroup          "BOM group
    variants          = l_t_variants          "Varients
    items             = l_t_itemdata          "Item details
    materialrelations = l_t_bom_head          "Header details
    itemassignments   = l_t_itemlink_to_var   "Item lineked to Varient
    return            = l_t_return.
LOOP AT l_t_return INTO l_r_return WHERE type CA 'AEX'.
l_f_error = 'X'.
ENDLOOP.
IF l_f_error = space.
    Processing successful --> Commit work on PDM system
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ELSE.
    Error in processing --> Rollback work on PDM system
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
ENDIF.
LOOP AT l_t_return INTO l_r_return.
WRITE:/ l_r_return-type, l_r_return-id, l_r_return-number,
          l_r_return-message.
ENDLOOP.
could you please help me to come out of this problem.

Hi,
Did you try creating manually through CS01 with the same data? There could be a customization setting to restrict like this.
Thanks,
Vinod.

Reg: Creation of BOM along with Alternative BOM

Hi Experts,
I have written the below code for creating BOM along with Alternative BOM, I'm getting the following error.
W BAPI1080             028
Error/warning when checking the structure of the BOM group with ID=
A BAPI1080             002
Basic data for (BOM) group available twice
A BAPI                 001
No instance of object type BOMGroup has been created. External reference:
W BAPI1080             028
Error/warning when checking the structure of the BOM group with ID=
A BAPI1080             002
Basic data for (BOM) group available twice
A BAPI                 001
No instance of object type BOMGroup has been created. External reference:
Please find the piece of code below.
SORT it_bom01 BY matnr idnrk posnr ASCENDING.
LOOP AT it_bom01 INTO wa_bom01.
    AT NEW matnr.
      CLEAR:
        it_bomgroup[],
        wa_bomgroup,
        it_variants[],
        wa_variants,
        it_items[],
        wa_items,
        it_matrel[],
        wa_matrel,
        it_itemas[],
        wa_itemas,
        it_return.
    ENDAT.
* Material BoM Group Header Data
    wa_bomgroup-bom_group_identification = 'IDENTIFICATION'.
    wa_bomgroup-object_type = 'BGR'.
    wa_bomgroup-object_id = 'ID'.
    wa_bomgroup-bom_usage = wa_bom01-stlan.
    wa_bomgroup-ltxt_lang = sy-langu.
    wa_bomgroup-technical_type = ' '.
*   wa_bomgroup-bom_text = .
    wa_bomgroup-created_in_plant = wa_bom01-werks.
    APPEND wa_bomgroup TO it_bomgroup.
* Header Details of the different variants
    wa_variants-bom_group_identification = 'IDENTIFICATION'.
    wa_variants-object_type = 'BOM'.
    wa_variants-object_id = 'ID'.
    wa_variants-alternative_bom = wa_bom01-stlal.
    wa_variants-bom_status = wa_bom01-stlst.
    wa_variants-base_qty = wa_bom01-bmeng.
    wa_variants-valid_from_date = wa_bom01-datuv.
    wa_variants-alt_text = wa_bom01-alt_text.
    wa_variants-function = 'NEW'.
    APPEND wa_variants TO it_variants.
* Details of the items of the variants
    wa_items-bom_group_identification = 'IDENTIFICATION'.
    wa_items-object_type = 'ITM'.
    wa_items-object_id = 'ID'.
    wa_items-item_no = wa_bom01-posnr.
    wa_items-item_cat = wa_bom01-postp.
    wa_items-component = wa_bom01-idnrk.
    wa_items-comp_qty = wa_bom01-menge.
    wa_items-valid_from_date = wa_bom01-datuv.
    APPEND wa_items TO it_items.
* Details of the materials of the different variants
    CLEAR it_matrel.
    wa_matrel-bom_group_identification = 'IDENTIFICATION'.
    wa_matrel-material = wa_bom01-matnr.
    wa_matrel-plant    = wa_bom01-werks.
    wa_matrel-bom_usage = wa_bom01-stlan.
    wa_matrel-alternative_bom = wa_bom01-stlal.
    APPEND wa_matrel TO it_matrel.
* Linking items to the corresponding variants
    CLEAR it_itemas.
    wa_itemas-bom_group_identification = 'IDENTIFICATION'.
    wa_itemas-sub_object_type = 'ITM'.
    wa_itemas-sub_object_id = 'ID'.
    wa_itemas-super_object_type = 'BOM'.
    wa_itemas-super_object_id = wa_bom01-matnr.
    wa_itemas-valid_from_date = wa_bom01-datuv.
    wa_itemas-function = 'NEW'.
    APPEND wa_itemas TO it_itemas.
    AT END OF matnr.
      CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'
        EXPORTING
          all_error         = 'X'
        TABLES
          bomgroup          = it_bomgroup
          variants          = it_variants
          items             = it_items
          materialrelations = it_matrel
          itemassignments   = it_itemas
          return            = it_return.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
      LOOP AT it_return.
        WRITE:/ it_return-type, it_return-id, it_return-number,
        it_return-message.
      ENDLOOP.
    ENDAT.
ENDLOOP.
Thanks and Regards,
Abdur Rafique

Hi Sree,
I used your code, I removed the levels because, i have only one level 'the lineitems'. Please find the modified code below. I'm not able to create the BOM, it throws an error as "BOM is recursive". I checked the header and item contents before passing to FM, it is correct.
Please help me with the solution.
REPORT zbom_sdn.
TYPE-POOLS: truxs.
DATA: bom_header     LIKE cad_bicsk,
      bom_item       TYPE TABLE OF cad_bom_item WITH HEADER LINE,
      bom_sub_item   TYPE TABLE OF cssubitem WITH HEADER LINE,
      dms_class_data TYPE TABLE OF cls_charac WITH HEADER LINE,
      sap_field_data TYPE TABLE OF rfcdmsdata WITH HEADER LINE,
      e_return       LIKE cad_return-value,
      e_message      LIKE message-msgtx,
      e_message_len LIKE cad_return-message_len.
DATA v_item TYPE i.
TYPES : BEGIN OF ty_data,
         matnr TYPE cad_bicsk-matnr," Material
         werks TYPE csap_mbom-werks," Plant
         stlan TYPE csap_mbom-stlan," BOM Usage
         datuv TYPE csap_mbom-datuv," Valid From
*         posnr TYPE stpo_api03-item_no," Item Number
         idnrk TYPE stpo_api03-component," BOM Component
         postp TYPE stpo_api03-item_categ," Item category
         menge TYPE cad_bom_item-menge," Quantity
         bmeng TYPE stko_api01-base_quan," Base Qty
         stlst TYPE stko_api01-bom_status," BOM Status
         stlal TYPE csap_mbom-stlal," Alternative BOM
         alt_text TYPE stko_api01-alt_text," Alternative BOM text
        END OF ty_data.
DATA : it_data TYPE TABLE OF ty_data ,
       wa_data TYPE ty_data.
DATA:   wa_raw TYPE truxs_t_text_data.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-001.
PARAMETER : p_file TYPE rlgrap-filename OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b2.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
    EXPORTING
      program_name = syst-repid
      dynpro_number = syst-dynnr
    CHANGING
      file_name     = p_file.
START-OF-SELECTION.
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
       EXPORTING
*       I_FIELD_SEPERATOR          =
         i_line_header              = 'X'
         i_tab_raw_data             = wa_raw     " Work Table
         i_filename                 = p_file
       TABLES
         i_tab_converted_data       = it_data[] " Actual Table
       EXCEPTIONS
        conversion_failed          = 1
        OTHERS                     = 2 .
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
CLEAR: bom_header, bom_item, bom_sub_item.
REFRESH: bom_item, bom_sub_item.
DATA : v_lineitem TYPE sposn VALUE '0000',
         v_slineitem TYPE sposn VALUE '0'.
LOOP AT it_data INTO wa_data.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        input = wa_data-matnr
      IMPORTING
        output = wa_data-matnr.
* fill BOM header
    CLEAR bom_header.
    bom_header-matnr = wa_data-matnr. "'000000000200000016'.
    bom_header-stlal = wa_data-stlal. " Alternative Bom
    bom_header-werks = wa_data-werks.                       "'1000'.
    bom_header-stlan = wa_data-stlan.                       "'3'.
    bom_header-bmeng = wa_data-bmeng.
    bom_header-cadkz = 'X'.
    bom_header-stktx = wa_data-alt_text.
*      bom_header-ztext = wa_data-text.
    bom_header-datuv = wa_data-datuv."'01.10.2010'.
* fill item
    v_lineitem = v_lineitem + 10.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        input = v_lineitem
      IMPORTING
        output = v_lineitem.
*    bom_item-upskz     = 'X'.     " If We hav the Sub items Enable it.
    bom_item-idnrk     = wa_data-matnr. "'000000000200000017'.
    bom_item-posnr     = v_lineitem.
    bom_item-postp     = wa_data-postp."'L'.
    bom_item-menge     = wa_data-menge.                     "'1'.
*    bom_item-fmeng     = wa_data-fqty.
    APPEND bom_item.
    CLEAR: bom_item.
    AT END OF matnr.
      CALL FUNCTION 'CAD_CREATE_BOM_WITH_SUB_ITEMS'
           EXPORTING
                i_bom_header   = bom_header
                i_auto_posnr   = ''
           IMPORTING
                e_return       = e_return
                e_message      = e_message
                e_message_len = e_message_len
                e_bom_header   = bom_header
           TABLES
                bom_item       = bom_item
                bom_sub_item   = bom_sub_item
                dms_class_data = dms_class_data
                sap_field_data = sap_field_data
           EXCEPTIONS
                 OTHERS         = 1.
      REFRESH bom_item.
      WRITE : e_message.
    ENDAT.
    CLEAR wa_data.
ENDLOOP.
Thanks and Regards,
Abdur Rafique

Printing Requirements

Hi...
My client has following printing requirements:
1.       Bank Payment u2013 vendor & others
2.       Bank Receipt u2013 customer & others
3.       Journal vouchers
4.       Purchase voucher (MIRO, and manual)
5.       Debit and Credit notes u2013 FI, MM, SD.
Bank Payment is made through F-53 & check is drawn in FBZ5. Now i am issuing the check to Vendor. When i issue check, i want to take sign on acknowldgement. Now how to print this payment letter. How to get this letter in SAP.
Also i want to credit & debit memo print format. I am not asking for JV print. Let me know how to take it in SAP.
Edited by: Deepak Agrawal on Sep 21, 2009 6:40 PM

For your printing requirements, you have to do the following thing
1. First identify the corresponding variant under Correspondence tab in the Fin Accounting Global setting
2. Then develop a custom form & attacch the same to the variant
3. Go to F.62, provide the input details & the corresponding varinat & you can print the data in the format as developed by you.
I hope you can't take printout of acknowledgement for the check issued through FBZ5. The best way would be to take the print out of the payment voucher (This will be a custom form, so you can include a place for reciever's signature) & get the signature when you are handing over the cheque.
If you need details of the corresponding variants, let me know the same.
Regards
R.Karthigayan

How to set user parameters in transaction MD61 through a report?

Hi,
I want to set default values for 'Requirement Type' in user parameters of transaction MD61 through a report. Please help.
Thanks in Advance.

Create Variant using SHD0 and with Group and assign to particular user's
Here is the steps
Creating a Variant Group
1. Open transaction SHD0, enter the transaction code, and press enter.
2. Choose the Standard Variants tab page, and then the sub tab page Variant Groups, and enter a group name, such as GROUP_GEN
3. Choose Create. Enter a short text on the Maintain Variant Group window that appears and save the variant group.
Assigning Users
Once you have created the variant group and the relevant transaction variants with screen variants, you now need to assign users to the variant group as follows
1. Return to the Standard Variants tab page, Variant Groups sub tab page.
2. Enter the name of a user that you want to assign to this variant group, and choose Assign. A message that this user was successfully assigned to the variant group appears in the status bar. If you choose a where-used list for users, this user is displayed in the user list.
3. However, for the screen variants of the variant group that you created above to be displayed for the user, you first need to select Set Proposal. The user is assigned to the group and the associated transactions are started with the corresponding variants only once you choose the Set Proposal function.
You can use this procedure of user assignment for all other users that you want to add to the variant group
Hope this helps.
Thanks
S.N

How to trigger an ABAP program in a Process chain

Hello Forum,
1. In a process chain, if a program fails, how can we re-run it?
2. If the process preceeding the ABAP program fails, how can we start the program?
3. If an Infospoke fails in a process chain, how can we trigger that?
Thank you,
Its my pleasure to assign points,
raj

Hi,
1. U have to first check whats the reason for the failure. check in the monitor screen details button, the error message will be displayed, check the error, correct it. and to proceed with further right click on the subsequent process use Repeat option , the loads will get continue.
2. same here, if it fails check the reason, sometimes if two parallel process trying to access the same program Lock may occur, stop one process, once its done start the second process, use the transaction code SA38>select ur ABAP program, the corresponding variant->this is for running the ABAP program in the backgroud..if u want to run direct means Select the Process types Under the general services u find an ABAP program
3. same here too u should find the reason why it fails, and rectify the error, and use the repaet option to proceed with further.

Setting layout to a report in background job

Hi.
Does anybody knows how I set layouts dynamically to a report output, given that such report is scheduled to run once a day in a background job?
It would work for me, either: through SM36 or coding JOB_OPEN / JOB_SUBMIT / JOB_CLOSE (or any other option, if available).
My requirement is to execute every night few reports, each with their corresponding variants and layouts.
Something like:
RUN <report1> VARIANT <variant1> LAYOUT <layout1> JOB <job>. (it would output and xls file).
RUN <report2> VARIANT <variant2> LAYOUT <layout1> JOB <job>. (it would output another xls file).
RUN <report3> VARIANT <variant3> LAYOUT <layout2> JOB <job>. (it would output a 3rd xls file).
How should I do to inform variant and layout parameters?
Thank you.
Rafael.

I think I didn't make myself clear in my explanation. Sorry about that.
My question is, I can create a new field in selection-screen specifically to layout and it would work. However, as I'm running it in background, the ALV will not be shown and the output file must be the export of the ALV with the layout (if in XLS, it'd be even better, but in .CSV would work as well). I just don't think it would work with a .TXT output, because there's no way to reflect the layout in a .TXT file.
Is there any way of having the ALV inside the output file (saved in the server, in background processing)?
Thank you so much!
Edited by: rvsilvax on Nov 30, 2011 3:45 PM

Correspondance variant

Similar Messages

Maybe you are looking for