Create incident via BAPI_BUS1240_CREATE
hi Masters,
i have problem of creating an incident in TCODE : CBIH82.
i found a bapi BAPI_BUS1240_CREATE to create an incident in TCODE : CBIH82.
can anyone tell me as to how to use this bapi. sample code is much appriciated.
thank you,
pasala.
Hi Jacobkata, how are you? Good?
I have been trying to execute this BAPI: BAPI_BUS1240_CREATE it has been more than one week And I stil didn't figure out how to execute it. Do you still have this BAPI? Could you send me the print screens from the LSMW Steps?
Because an error occured and I don't know what is wrong.
IT says: Function module not allowed: BAPI_IDOC_INPUT1 (the function module ‘BAPI_IDOC_INPUT1’ and the object category application determinado is not allowed to IDoc.
I already followed all the steps that is on page http://scn.sap.com/thread/63515 to try to find the error on it but I can find.
Do you have any idea how I can fix it or find which exactly error is?
A friend of mine here said I should include all mandatory fields.. but I don't know which are the mandatory fields and which value/data or rule I should include on these...
Could you kindly help me?
Thanks Samanta
Similar Messages
-
Create Incident via CRM_UI, non-SAP components depending of sold-to-party
Hello!
We are using CRM_UI on Solman 7.1 ( SPS 10 ) to create Incidents. On the 3'rd step there is option to select SAP Components or non-SAP Components if defined. We are using a lot of non-SAP components.
Is it possible to prevent users to choose all SAP component, only few of them depending of customer ( BP sold-to-party )? Does it exist authorisation object for this?
Thank's in advance!
Best regards,
RenatoHello,
Please run SPRO tcode and search for
Maintain User Application Components
Use
This activity maintains your application components. Create your own component hierarchy, and add it to the default SAP application components.
Recommendation: Choose component names that are easy to recognize and distinguish.
Activities
1. Specify a component. If your components are hierarchical, enter the leading component first.
2. Enter a description of the component.
3. Specify the hierarchy level of the component (01-0n). Create the component hierarchy top-down.
4. Specify the node type. Use node type 0 for a header, and 1 for normal nodes.
5. Flag whether the node is selectable.
6. Save.
To configure the display of value help in the SAP component search, edit the VH_SAPCOMP_TREE parameter in the Define Parameters activity.
BR,
K. -
Updating Requisition No while creating PO via FM-BAPI_PO_CREATE1
Hi ,
Our requirement is creating Po via FM BAPI_PO_CREATE1 and we are passing data from other Application through that BAPI. Tracking field of the Application with SAP is only Requisition No.
I want to know in which field of that BAPI I'll make the entry to update Requisition No. of PO?
Thanks & Regards,
Biswajit
Edited by: Biswajit Das on Jan 11, 2009 8:36 PMHi bisjwat.
In the tabpi u have table paremeters.
In that u chave poitem type BAPIMEPOITEM.
with in the BAPIMEPOITEM u have the field 'PREQ_NO'.
this is the field for the po requistion number.
I think it will solve u r problem.
Thanks -
Remove Templates from Create Incident From Template Selection
Originally all users had access to all of the templates created, however now that we have been using SCSM for a while the number of templates created has started to grow and make the Create Incident From Template Screen difficult to navigate. I am
trying to limit the number of templates each team sees based on security group, however when I uncheck the templates from the Form Templates section of the User Role, they continue to display for all users. Is there somewhere else I have to go in and
change this that I am missing?Hi,
Take a look at this thread:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/d0b64ab8-ea5a-4426-968e-77675193473f/hiding-templates-from-console-users-while-still-effectively-using-the-end-user-role?forum=administration
(By default the End User role has access to all templates, and the members of that role is Authenticated Users)
Regards
//Anders
Anders Asp | Lumagate | www.lumagate.com | Sweden | My blog: www.scsm.se -
How to create a via from layer 1 to 3 on a 8 layer PCB?
I'm working on a design for a 8 layer PCB with Multisim/Ultiboard v10. In Multisim under sheet properties i selected the PCB to contain 8 layers, which makes Ultiboard to create this board with 4 layer pairs and 0 top/bottom build-ups. In the PCB properties of Ultiboard i enabled micro vias and buried/blind vias but i noticed that i'm not able to allow vias between some combinations of layers.
For example i can enable vias from top to the second layer (1st inner) and from top to the fourth layer (3rd inner), but not from top to the third layer (2nd inner).
When placing a via, i can select top for the start and the 3rd layer
for the end, but it will be created as via between top and the 4th
layer, which will -of course- shorten several traces on the 4th layer.
So my questions is: Why am i not allowed to create a via, that goes from the top layer to the third layer and how to enable all possible combinations of start and ending layers for the via?
Thanks for your help
fhn
PS: sorry for my bad english :/
Message Edited by fhn on 08-22-2008 04:39 AMI am not 100% sure about this, but what I see happening here is that you can only select certain combinations of pairs. Once that selection is made it will gey out other selections as not valid. You might want to carefully look at the options in the via selection and make sure of which layers you want vias to be on. I don't know about enabling all layers in this selection. I would assume this would not be legal from a design rules standpoint, but since most of my boards are either single or double sided I do not have the necessary experience with multi-layers to give a proper answer to that.
This is the only thing I can advise as when I went through the process I was able tio select the vias for the layers you outlined in your post.
I hope this helps somewhat as this is all can tell you.
Kittmaster's Component Database
http://ni.kittmaster.com
Have a Nice Day -
Issue with permission while creating incident
We have an issue. Sometimes our analytics get "no sufficient permission to perform the operation".
First of all they assigned roles with different queues. They have access to edit incidents with user role profile advanced operators and queue for incidents with status New. And they have access to read incidents with user role profile read-only operator
and queue for incidents with statuses Closed or Canceled.
When open new form for creating incident and wait a few minutes they may can't save incident and get permission error. But object in newly opened incident form isn't added in any queues. And then I find that incident was actually created.
Also when they save incident successfully, they can't even see it for up to 5 minutes while incident isn't in queue.
That's really annoying and confusing. As I can't get any way to troubleshoot what exactly form can't save.
Any workarounds to this? Or how do you separate access to closed and active incidents?Hi
Rather than creating queues for these, you may be better creating Views for this instead, unless you specifically need to deny access to work items in these states.
Queue membership is calculated on a schedule and incurs a performance overhead. Therefore I tend to use these sparingly for things like support group separation and SLO targeting.
Also, if your analysts are opening an incident and waiting for a while, it is likely that a background workflow is updating the incident while the analyst has the record open. This will prevent the changes from being committed and will generate an
error.
HTH
Shaun -
How to launch the Create Incident page as the Home Page
Hi All,
My issue is to launch the Create Incident page as the Home Page in the Service Pro Role.
To launch the Create Incident page as the Home Page is there any SPRO Configuration or we have to do through the code?
Thanks & Regards,
VenkatHi Venkat,
This can be done in the navigation bar configuration. Go to the path below and select your navigation bar profile, next to the description of your navigation bar profile there is a link ID, replace the home work centre logical link SRV-HOM-WC with this link SRV-INC-CR.
When you now log into your business role the incident creation screen should display instead of the service home screen
SPRO --> CRM --> UI Framework --> Technical Role Definition --> Define Navigation Bar Profile
Regards,
David. -
Config settings to gray out "Reqted Qty" field while creating TO via LT03
Hi Experts,
Could anyone please me in this. I would like to gray out "Requested Quantity" field when creating TO via LT03 transaction. Can anyone please let me know where the config setting needs to be maintained inorder to gray out the "Requested Quantity" in LT03 transaction.
Thanks for your help.
Regards,
NagarjunHi,
no there is not such a functionality.
From a field settings perspective you may work at account group level, =>OBD2 or OVT0
and/or at transaction type level => OB20
With OB20 you can distinguish between creation and change.
You may also react per authorisation. See F_KNA1_EAN. In that case you may gray out fields individually.
BR
Alain -
Prob in activating a field in delivery while creating delivery via VL04
hi thx i am also facing the same prob. this badi is working while creating deliveries via VL01N OR VL02N but if we are creating delivery via VL04 this badi is not working, can u please guide me.
thanx in adv.In the Import parameter TECHN_CONTROL one field called SENDER_SYSTEM is there, it takes the Logical System Name(Default will be Local System). Check whether it is defined or not. This can be viewed in SALE tranasction.
Tcode SALE > Basic Setting>Logical System-->Assign Logical System to client.
Here You check ur Client is assigned logical System Name or Not?
Debug your program and check this value....
It will resolve ur prob.. -
Spell check missing from create incident form in RC
I have noticed auto spell check is missing from the create incident form in RC. Is there anyway to turn this on?
usually i'm against blatant necromancy like this, but with
the Phoenix, there's a real case for this feature. Maybe call in Word's spelling engine?
while we're at it, maybe we could fix the RTF weirdness in knowledge articles? -
SCSM 2012 - creating incident fro email - description issue
Hello, I have SCSM 2012 RTM and I am trying to use out-of-the-box create incident from e-mail functionality.
It is working but I have issue with description field of created incident- it comes with the last part of the eml file.
Description field of Incident looks like :
-_000_47499D6C4A5DAE4EB0FF86A4F6184D7EFB0023D9ex2010mbx1podra_
Content-Dis; filename="winmail.dat"
Content-Transfer-Encoding: base64 .....
I can not use Exchange Connector because I can not install SP1 for SCSM 2012 - Service Manager databases are on SQL 2008 - which is not supported for SP1 for SCSM 2012.
Any help is welcome.
Best regards,
DubravkoThanks for your reply, but my Service manager databases are on consolidated SQL 2008 SP2 cluster.
SQL 2008 SP2 is not supported for SCSM 2012 R2. Because on that SQL 2008 SP2 cluster are also other bussiness databases which has some compatibility issues I can not do the upgrade to SQL 2008 R2.
Best regards,
Dubravko -
SCSM 2012 - creating incident from email - description issue
Hello, I have SCSM 2012 RTM and I am trying to use out-of-the-box create incident from e-mail functionality.
It is working but I have issue with description field of created incident- it comes with the last part of the eml file.
Description field of Incident looks like :
-_000_47499D6C4A5DAE4EB0FF86A4F6184D7EFB0023D9ex2010mbx1podra_
Content-Dis; filename="winmail.dat"
Content-Transfer-Encoding: base64 .....
I can not use Exchange Connector because I can not install SP1 for SCSM 2012 - Service Manager databases are on SQL 2008 - which is not supported for SP1 for SCSM 2012.
Any help is welcome.
Best regards,
DubravkoThanks for your reply, but my Service manager databases are on consolidated SQL 2008 SP2 cluster.
SQL 2008 SP2 is not supported for SCSM 2012 R2. Because on that SQL 2008 SP2 cluster are also other bussiness databases which has some compatibility issues I can not do the upgrade to SQL 2008 R2.
Best regards,
Dubravko -
How to create incident rule for SOA composite faulted instances
Hi Experts,
How can I create an incident rule for creating an incident when a SOA composite instance goes faulted. I want to notify the administrator when any of the SOA composite instance gets faulted but I am not able to undestand in my incident rule what type of event should be used,in-short I am not able to understand how can I create a rule for eveluating SOA composite faulted instances.
I am posting this query third time here. Please suggest me a solution or is this a limitation of OEM 12c Cloud Control ?
Please help...its eally urgent!!!Creating Incident rules is a very simple process as long as you know what event you wanna create your rule one. In your case specifically, its even more simple since you already know your target type and metric name.
Steps:
1) Create a rule set.
2) On the same page hit "Targets" tab and select "All target types" and select "SOA Composite" from the target type list.
3) Now hit "Rules" tab and then hot "Create" and then select first radio button - "Incoming events" since you wanna wrap SOA composite fault metric alert event into a rule.
4) Now select "Type" and select "Metric Alert"
5) Now since you are interested in a "specific event" - SOA composite fault metric alert event, select that radio button and hit "Add"
6) From the "Target Type" dropdown, select "SOA Composite" target type and type "%Fault%" in the Metric name textbox and hit Search.
7) Select you Metric name and select you severity as you wish.
8) Add Actions - create notification, emails etc. (Refer docs to understand how best you can use these options as needed)
9) Save your rule and save your Rule set.
You have a rule (Make sure its enabled) that will execute your specified actions when any SOA Composite will breach your the selected metric (Fault metric in your case) -
Hi all,
Can anyone give me some pointers when creating Routings via LSMW. I see there are two standard uploads in RCPTRA01 and RCPTRA02. However, the mapping structures seem to be different between the two.
I need to add PRT's material assignments and long texts to the routing.
Any help greatly appreciated.Hi,
Use standard batch/Direct input : RCPTRA02
Source Fields
MATERIAL_ROUTING Material
PLNAL C(002) Group Counter
MATNR C(018) Article Number
WERKS C(004) Site
OPERATION_ROUTING Operations
PLNAL C(002) Group Counter
VORNR C(004) Operation/Activity Number
STEUS C(004) Control Key
ARBPL C(008) Work center
WERKS C(004) Site
LTXA1 C(040) Operation short text
MEINH C(003) Quantity unit for operation (batch input)
BMSCH C(017) Base quantity (Batch input)
LAR02 C(006) Activity Type
VGE02 C(003) Unit for the standard value (batch input)
VGW02 C(011) Standard Value (Batch Input)
LAR03 C(006) Activity Type
VGE03 C(003) Unit for the standard value (batch input)
VGW03 C(011) Standard Value (Batch Input)
COMPONENT_ROUTING Components
PLNAL C(002) Group Counter
VORNR C(004) Operation/Activity Number
POSNR C(004) BOM Item Number
MATNR C(018) Article Number
WERKS C(004) Site
Field Mapping and Rule
RC271_DS Work center structure for direct input (for datasets)
Fields
TCODE Transaction Code
Rule : Constant
Code: RC271_DS-TCODE = 'CA01'.
STTAG Character Field Length = 10
Rule : Constant
Code: RC271_DS-STTAG = '18.03.2014'.
AENNR Change Number
REVLV Revision Level
WERKS Site
Rule : Transfer (MOVE)
Code: RC271_DS-WERKS = MATERIAL_ROUTING-WERKS.
PROFIDNETZ Profile
PLNNR Key for Task List Group
PLNAL Group Counter
Rule : Transfer (MOVE)
Code: RC271_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
STATU Status
Rule : Constant
Code: RC271_DS-STATU = '4'.
VAGRP Responsible Planner Group/Department
Rule : Constant
Code: RC271_DS-VAGRP = 'KD1'.
VBELN Sales Document
POSNR Character field of length 6
PSPNR Work Breakdown Structure Element (WBS Element)
MAPL_DI_DS Assign routing to article for direct input (for datasets)
Fields
ACTTYP Processing type for objects to be imported
Code: MAPL_DI_DS-ACTTYP = 'H'.
MATNR Article Number
Rule : Transfer (MOVE)
Code: MAPL_DI_DS-MATNR = MATERIAL_ROUTING-MATNR.
WERKS Site
Rule : Transfer (MOVE)
Code: MAPL_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
PLNAL Group Counter
Rule : Transfer (MOVE)
Code: MAPL_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
LIFNR Vendor Account Number
KUNR Account Number of Customer
SUCHFELD Search Field for Customer-Specific Task List Selection
VBELN Sales Document
POSNR Sales Document Line Item (Batch Input Field)
PSPNR Work Breakdown Structure Element (WBS Element)
PLKO_DI_DS Header structure for direct input (for datasets)
Fields
ACTTYP Processing type for objects to be imported
Code: PLKO_DI_DS-ACTTYP = 'H'.
PLNAL Group Counter
Rule : Transfer (MOVE)
Code: PLKO_DI_DS-PLNAL = MATERIAL_ROUTING-PLNAL.
VERWE Use by user or system
Rule : Constant
Code: PLKO_DI_DS-VERWE = '1'.
WERKS Site
Rule : Transfer (MOVE)
Code: PLKO_DI_DS-WERKS = MATERIAL_ROUTING-WERKS.
STATU Status
Rule : Constant
Code: PLKO_DI_DS-STATU = '4'.
PLNME Unit of measure for the task list (batch input)
Rule : Constant
Code: PLKO_DI_DS-PLNME = 'KG'.
LOSVN From lot size (BTCI)
Rule : Constant
Code: PLKO_DI_DS-LOSVN = '0'.
LOSBS To lot size (BTCI)
Rule : Constant
Code: PLKO_DI_DS-LOSBS = '999999999'.
VAGRP Responsible planner group/department
Rule : Constant
Code: PLKO_DI_DS-VAGRP = 'KD1'.
KTEXT Task list description
Rule : Constant
Code: PLKO_DI_DS-KTEXT = 'Article Routing'.
TXTSP Single-Character Indicator
PLPO_DI_DS Routing/item structure for direct input (for datasets)
Fields
ACTTYP Processing type for objects to be imported
Code: PLPO_DI_DS-ACTTYP = 'H'.
PLNAL Group Counter
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-PLNAL = OPERATION_ROUTING-PLNAL.
PLNFL Sequence
Rule : Constant
Code: PLPO_DI_DS-PLNFL = '000000'.
VORKN Node number (batch input)
VORNR Operation/Activity Number
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-VORNR = OPERATION_ROUTING-VORNR.
UVOKN Node number (batch input)
UVORN Suboperation
STEUS Control key
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-STEUS = OPERATION_ROUTING-STEUS.
ARBID Object ID (batch input)
OBJTY Object types of the CIM resource
ARBPL Work center
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-ARBPL = OPERATION_ROUTING-ARBPL.
WERKS Site
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-WERKS = OPERATION_ROUTING-WERKS.
KTSCH Standard text key
LTXA1 Operation short text
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-LTXA1 = OPERATION_ROUTING-LTXA1.
MEINH Quantity unit for operation (batch input)
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-MEINH = OPERATION_ROUTING-MEINH.
UMREN Denominator for conversion from unit to base unit (BTCI)
Rule : Constant
Code: PLPO_DI_DS-UMREN = '1'.
UMREZ Numerator for converting from unit to base unit (BTCI)
Rule : Constant
Code: PLPO_DI_DS-UMREZ = '1'.
BMSCH Base quantity (Batch input)
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-BMSCH = OPERATION_ROUTING-BMSCH.
ZMERH Break time (batch input)
ZEIER Unit for break time (batch input)
LAR01 Activity Type
VGE01 Unit for the standard value (batch input)
VGW01 Standard Value (Batch Input)
LAR02 Activity Type
VGE02 Unit for the standard value (batch input)
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-VGE02 = OPERATION_ROUTING-VGE02.
VGW02 Standard Value (Batch Input)
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-VGW02 = OPERATION_ROUTING-VGW02.
LAR03 Activity Type
VGE03 Unit for the standard value (batch input)
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-VGE03 = OPERATION_ROUTING-VGE03.
VGW03 Standard Value (Batch Input)
Rule : Transfer (MOVE)
Code: PLPO_DI_DS-VGW03 = OPERATION_ROUTING-VGW03.
PLMZ_DI_DS Article component allocation for direct input(for datasets)
Fields
ACTTYP Processing type for objects to be imported
Rule : Constant
Code: PLMZ_DI_DS-ACTTYP = 'H'.
PLNAL Group Counter
Rule : Transfer (MOVE)
Code: PLMZ_DI_DS-PLNAL = COMPONENT_ROUTING-PLNAL.
PLNFL Sequence
Rule : Constant
Code: PLMZ_DI_DS-PLNFL = '000000'.
PLNKN Node number (batch input)
VORNR Operation/Activity Number
Rule : Transfer (MOVE)
Code: PLMZ_DI_DS-VORNR = COMPONENT_ROUTING-VORNR.
STLTY BOM category
Rule : Constant
Code: PLMZ_DI_DS-STLTY = 'M'.
STLNR Bill of material
Rule : Constant
Code: PLMZ_DI_DS-STLNR = '00000005'.
STLAL Alternative BOM
Rule : Constant
Code: PLMZ_DI_DS-STLAL = '01'.
STLKN Node number (batch input)
POSNR BOM Item Number
Rule : Transfer (MOVE)
Code: PLMZ_DI_DS-POSNR = COMPONENT_ROUTING-POSNR.
WERKS Site
Rule : Transfer (MOVE)
Code: PLMZ_DI_DS-WERKS = COMPONENT_ROUTING-WERKS.
BOMAT Article Number
Rule : Transfer (MOVE)
Code: PLMZ_DI_DS-BOMAT = COMPONENT_ROUTING-MATNR.
STLST Order level
STLWG Order path
STLTY_W BOM category
Rule : Constant
Code: PLMZ_DI_DS-STLTY_W = 'M'.
STLNR_W Bill of material
Rule : Constant
Code: PLMZ_DI_DS-STLNR_W = '00000005'.
STLAL_W Alternative BOM
Rule : Constant
Code: PLMZ_DI_DS-STLAL_W = '01'.
Map the extra fields according to your requirement. Hope you'll find the code helpful. -
Encounter error message 61062 when create PR via ME51
Dear Consultant,
I encountered error message 61062 - "dd.01.2011 date comes after end of valid factory calendar. (Pls correct)" when create PR via transaction ME51. Although I have changed the Delivery date to "31.12.2010", system still issue error message. FYI, material that I used to create PR has planned delivery time = 185 days (pre-configured by our purchaser via Purchasing info.record) which is equivalent to dd.01.2011. Our factory calendar is configured valid up to Year 2010 and the new year (2011) will only be configured at end of December.
If using transaction ME51N to create PR for the mentioned material above (with delivery date entered as 31.12.2010), there is no error message being issued by the system. May I know is there any solution to transaction ME51?
Pls advise asap.
Thanks & regards,
LOI>
LOI wrote:
> May I know if there Is any effect for other modules like PP/PM on changing plant calender to 2011?
yes, a positive effect, you will not receive error messages because of missing calender anymore.
I have my calendars maintained until 2015
ME51N only takes an info record into account when you do source determination, without source determination, the planned delivery time from material master is taken.
Maybe you are looking for
-
I have a late 2012 iMac and a late 2009 mac mini. I want to know if I can take the 8 GB of ram from the iMac and install it in my mac mini. According to Cruicial my mac mini could use: Module Size: 8GB Kit (4GBx2) Package: 204-pin SODIMM Feature: DD
-
Why is my macbook pro making a click sound?
I've only brought it about 4 or 5 weeks ago and today I've just heard a like a really faint rattle like click sound? if i put my ear to it it sounds like its coming from the fan? i havent dropped it or damaged it so what could it be? hope theres noth
-
Troubles with iPhoto 11 Upgrade.
I have recently upgraded to iphoto 11 and the install went great, but now it is common for it to crash during import and when working on photos. What gives? I never had this problem before. Also the crop tool is odd when pic is vertical and I want
-
I found that when I zoomed into the sequence a lot using the +- keys, that the error message "..\..\Src\AudioRender\AudioPrefetch.cpp-99" kept jumping out at me. It was the last 3 steps of zooming in or out that brought the error message up on screen
-
Tabs in Safari close very slowly.
Closing tabs in Safari is painfully slow. This problem happens intermittently, with no discernable pattern. It is unaffected by the number of tabs that I have open. It occurs whether I press cmd+T, or whether I close a tab using the mouse. Closing on