Weblog: BSP extension for embedding word

In our project we have created a BSP Extension that allows MS Word to be embedded as an editor. Changes to the contents are loaded retrieved in WML and can be accessed in do_handle_data.
I can't find a similar weblog. If there is interest I will create a weblog describing how to create the extension.
Regards
John

Hi John,
We will be very much interested in the solution. Please post it as a weblog/code sample.
Thanks in advance.
Regards
Raja

Similar Messages

Kodo extensions for embedded fields

Hi,
I have the following situation: having input source, i generate persistent
classes and basic metadata for them. Then mapping tool creates a schema
and adds mapping information to this metadata as well.
Some of entities are marked embedded, but now i generate metadata for it
in a separate file. The problem is, that i want to specify externalization
extensions for these embedded entities, but Mapping tool does not transfer
this information into updated metadata files:
Assume there is an entity Trade, that has stateModel entity. stateModel is
embedded into trade. State model contains several enumeration attributes,
that have externalization extensions defined, to allow proper persisting/
loading from primitive attributes. Here is an excerpt from metadata for
state model after mapping tool has been run:
<?xml version="1.0" encoding="UTF-8"?>
<jdo>
<package name="com.bear.fi.tradehub.domain.trade">
<class name="TradeStateModelJDO">
<extension vendor-name="kodo" key="jdbc-class-ind-name"
value="none"/>
<extension vendor-name="kodo" key="jdbc-class-map"
value="none"/>
<field name="allocationStatus"
persistence-modifier="persistent">
<extension vendor-name="kodo" key="externalizer"
value="getByName"/>
<extension vendor-name="kodo" key="factory"
value="getByCode"/>
<extension vendor-name="kodo" key="jdbc-field-map"
value="none"/>
<extension vendor-name="kodo" key="jdbc-size" value="1"/>
</field>
</class>
</package>
</jdo>
However, the metadata for Trade itself (field stateModel) looks like:
<field name="state" embedded="true">
<extension vendor-name="kodo" key="jdbc-field-map"
value="embedded">
<extension vendor-name="kodo" key="allocationStatus">
<extension vendor-name="kodo" key="jdbc-field-map"
value="blob">
<extension vendor-name="kodo" key="column"
value="ALLOCATIONSTATUS"/>
</extension>
</extension>
i.e. field type is blob, not CHAR or INTEGER as the return type of
externalizer method is.
Is there any way to force Mapping tool to use initial metadata of embedded
fields as well, when generating metadata for owning object?
Thanks,
Egidijus

Unfortunately, no. Does it work if you manually change the mappings to
value mappings?Yes, it does. Actually i found out, that i left a mistake in generator,
therefore KODO was not able to determine return type of externalizer
method. Once i've fixed this, i get correct schema being generated without
transfering metadata to owning entity.
Egidijus

How to create BSP extension for ranges

Hi Experts,
I am trying to create a ranges like selection option means when we click on SAP ABAP selection option, it shows us the all possible option like eqal to, not equal to etc.
I have found a link as "/people/thomas.jung/blog/2006/01/13/custom-bsp-extensions-time-stamp-and-range-ui-elements but there is no step by step procedure for the same. Please help me out to provide the steps.
Thanks.
Jaten Sangal

Hi Jaten,
In the Blog you mentioned, there are links for the articles/code samples at the end.
quick link for the same is
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1e324092-0801-0010-a181-c8b0c54119e3?quicklink=index&overridelayout=true
Regards,
Ravi

BSP extension for popu

Hi, Can some one tell me if there is some way to build a BSP extension to pop up some pdf docment in a new window when clicked on a link.
It is like i need a bsp extension, in which i embed javascript to popup window.
Can some one help me?

Welcome to SDN..
Look at the below link..
/people/sap.user72/blog/2004/11/10/bsphowto-generate-pdf-output-from-a-bsp
/people/mark.finnern/blog/2003/09/23/bsp-programming-handling-of-non-html-documents
* Reward each useful answer
Raja T

Extension for Embedding Room Parts in Room Templates

Hi,
I am working on SAP Portal EP6.
I have created a room template and I would like to embed a part room template to my room template.
I am following the instructions on this page:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/44/e0c3b27db603fbe10000000a1553f6/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/44/e0c3b27db603fbe10000000a1553f6/frameset.htm</a>
The problem is that when I add an extension, I do not have the extension point "ON_FINALIZE_CREATE_ROOM".
The second one is that I olny have access to the room templates in the Template ID box !!
I would like to add the SAP_Public_Documents to my template.
Any solution ??
Thanks a lot...
Message was edited by:
Thibault Schalck

Hi,
which SPS are you using? This feature is new with SPS19
See: http://help.sap.com/saphelp_nw04/helpdata/en/45/0f5632a05f6c32e10000000a114a6b/frameset.htm
Kind reagrds
Karin

Problem in following the webblog "Using TimeStamps: BSP Extensions"

I try to follow the webblog "Using TimeStamps: BSP Extensions for a TimeStamp UI."
However, after I have created the method 'RESOLVE_MODEL_BINDING' and compiled it, it shows me an error message
'Method "ADD_TO_CHECK_TABLE" is unknown or PROTECTED or PRIVATE.'
This is some part of that code.
model = m_page_context->get_model( model_name ).
name = model->get_attribute_name( attribute_path = value_path ).
valuelow = model->get_attribute( attribute_path = value_path ).
IF id IS INITIAL.
 id = name.
ENDIF.
IF disabled IS INITIAL.
 bspmodel ?= model.
 bspmodel->add_to_check_table( control_id = name ).
ENDIF.

I defined the bspmodel above the if block like the tutorial code.
DATA: model TYPE REF TO if_bsp_model_binding,
 model_name TYPE string,
 metadata TYPE REF TO if_bsp_metadata_simple,
 metadata_base TYPE REF TO if_bsp_metadata,
 value_path TYPE string,
 is_valid TYPE i,
 error_value TYPE string,
 bspmodel TYPE REF TO if_bsp_model.
I further looked into the interface if_bsp_model in my system. It doesn't include any interface, and only five methods were found:
1) INIT
2) GET_BINDING_INTERFACE
3) GET_ERRORS
4) INSTANTIATE
5) RESET_ERRORS

How to create an link to an BSP-Extension in documentation

Hello everybody,
I've got an perhaps easy question. I want to create an link in my documentation to the documentation of an BSP-Extension (for example <htmlb:inputField>) Is here someone who can tell me the best way to do this?
If I use the function to insert links in docus, I don't find a Documentation Class that fits.
I already looked to the docu of the BSP-Extension (in edit-mode) and see, that say use the function "Internet Service" but it don't run.
What's to do?
Thanks for help.
Bye Matthias

Hi Matthias,
just go into your document e.g. via se61, in edit mode and do the following: Enter this link syntax:
<DS:IS.HTMLB INPUTFIELD>inputfield</>
Please note that IS is the technical name of the BSP-Extension objects, then comes the name of the extension itself, in this example it's htmlb, followed by several blanks (they are part of the name and thus very important) and then the name of the element in capital letters.
You can find this technical name of an existing docu object if you are in the SAPscript editor and select Extras -> Information -> For document.
Instead of using the syntax for links directly (i.e. <DS:IS:Extension-name followed by blanks and extension itself>name</>) you can also use this function in the SAPscript editor for long texts:
Insert -> Link, then choose document class BSP-Extension-Object via F4 and enter the name of the extension, the extension element and the text to be displayed in the document. However, this document class is not always visible via F4, so you'd better use the direct link syntax mentioned above to be on the safe side.
Hope this helps.
Regards, Heidi

Spring Console extension for weblogic 10.0

Hi,
I am trying to configure spring console extension for weblogic version 10.0 . As mentioned in some documents, I am unable to find the required jars in the server lib folder, and googled to download it, but yet no success. If any one is aware of where can I get the required jars and steps to configure spring console for version10.0, let me know.
Thanks

Hi
To my surprise, When i asked my Server team to get me weblogic support, I got a response from them stating that weblogic will not support spring framework 2.5 and they sent me the link
http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs100/100_over/overview.html#1131715
And asked me to downgrade my project to the supported version.
But I think it is not correct, I don't have information if really my local team contacted weblogic support, or they are just sending me this link based on the document they have.
But I don't understand why it is so hard to get this thing working. Is there many people facing this issue ?
Or every one using apache Axis2 or CFX for web service and spring webservice is not advised ?
Some time I don't know whom should be blamed.
Thanks

Bindable attribute for BSP elements in BSP extensions

Hey all
Can anyone explain what the 'Bindable' attribute in BSP elements, in BSP extensions, is for? It has no F1 help documentation and is not documented in the SAP library with the rest of the BSP element attributes.
Many thanks
Mark

Which field is? Has translate value content to spanish for this field?.
In SAP CRM UI, press F2 and tell me which is the field

LiveCycle Rights Management ES Extension for Microsoft Office(other locale)

After I've downloaded Rights Management ES Extension and installed it, I open Office Word, it said the language found in my locale is not supported, my company is using Chinese Version Office 2007, is there any workaround solution for it?
I have encountered a problem in my company...... my comapny has around 1 million documents need to apply policy, and many of those have another documents embedded in the parent document. When I use LC PDF Generator to convert, those embedded file(s) would become an icon image and the content is lost. So I want to apply the policy directly on the document, but seems that doesn't support Chinese Office.
Thanks and regards,
Bearyung

Currently, the Rights Management ES Extensions for Microsoft Office plugin is only supported on English, French, Geman and Japanese versions of Office.
http://help.adobe.com/en_US/livecycle/8.2/lcrmext_releasenotes.htm#DocumentationSet
Steve

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

MapViewer Extensions for JDeveloper11g

There is any MapViewer Extension for JDeveloper11g?
There is any change of the embeded dvt:map?
It seems that ithe dvt:map is not working with Mapviewer anymore - can't display the basemap data.
Thank you
Vio


Thank you for your answer.
The page is under public_html folder.
And here is the log from Jdeveloper:
{color:#000080}[Running application Application1 on Server Instance DefaultServer...]
---- Deployment started. ---- Oct 22, 2008 11:21:01 PM
Target platform is (Weblogic 10.3).
Running dependency analysis...
2008-10-22 23:21:01.812: Writing WAR file to C:\oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Application1\Application1-ViewController-webapp
2008-10-22 23:21:01.812: Wrote WAR file to C:\oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Application1\Application1-ViewController-webapp
2008-10-22 23:21:01.906: Writing EAR file to C:\oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Application1
2008-10-22 23:21:01.921: Wrote EAR file to C:\oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Application1
Deploying Application...
<Oct 22, 2008 11:21:02 PM EDT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Application1 is not versioned.>
Oct 22, 2008 11:22:22 PM com.sun.faces.spi.InjectionProviderFactory getProviderInstance
SEVERE: JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.
Application Deployed Successfully.
Elapsed time for deployment: 1 minute, 22 seconds
---- Deployment finished. ---- Oct 22, 2008 11:22:23 PM
Run startup time: 82016 ms.
[Application Application1 deployed to Server Instance DefaultServer]
Target URL -- {color}{color:#000080}http://127.0.0.1:7101/Application1-ViewController-context-root/faces/untitled1.jspx{color}
{color:#000080}Oct 22, 2008 11:22:25 PM oracle.adfinternal.controller.util.model.AdfmInterface initialize
INFO: ADFc: BindingContext is not present, not using ADFm APIs for DataControlFrames.
Oct 22, 2008 11:22:26 PM oracle.adfinternal.controller.metadata.provider.MdsMetadataResourceProvider <init>
INFO: ADFc: Controller caching of MDS metadata resources ENABLED.
Oct 22, 2008 11:22:26 PM oracle.adf.controller.internal.metadata.MetadataService$Bootstrap add
INFO: ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
{color}
Thanks,
Viorel

Search is not working for MS Word documents

Hi,
serious help required for search operation.
Search operation is not working for MS Word Documents.
i noticed that, after chekin word documents its status comes as
GENWWW.
i already enable file format & extension for word file.
can somebody help me in this regard.
Thankx in advance

Hi
Please enable the tracing option for :
requestaudit,indexer
Enable Full Verbose Tracing .
Checkin the Ms-Word document and once it fails then check the view server o/p under System Audit Information page and post the error message happening for indexing operation .
Thanks
Srinath

Problem with adobe livecycle rights management es2 extension for microsoft office

occurs several times an error message in Microsoft Office Excel that says it has experienced a problem with the complement of adobe livecycle rights management es2 extension for microsoft office if the message has appeared several times should disable the add and check for an update.
will refer to this error? as it has sought to upgrade and there is no error and remains not only to excel but also for word.
thanks in advance

Currently, the Rights Management ES Extensions for Microsoft Office plugin is only supported on English, French, Geman and Japanese versions of Office.
http://help.adobe.com/en_US/livecycle/8.2/lcrmext_releasenotes.htm#DocumentationSet
Steve

Is the BSP extension better than this solution(Text and Image in Button)?

Hi guys,
I have a concept question to decide whether a BSP extension is needed.
I want to put text and image in htmlb button, and used the solution like below:
<%
data image type ref to cl_htmlb_image.
data: image_string type string.
create object image.
image->id = 'back'.
image->src = cl_bsp_mimes=>sap_icon( id = '@9S@' ).
image->tooltip = 'Go back'.
clear image_string.
image_string = image->IF_BSP_BEE~RENDER_TO_STRING( page_context ).
 %>
 <xhtmlb:toolbarButton id = "back"
 onClick = "back"
 text = "<%= image_string %>" />
But this solution is not desired by customer, since they don't think it looks nice. So is it possible to create my own BSP extension to get a nicer element?
Thanks for any hint.
Regards,
Liying

Hi,
By a nicer element...did you mean to display a better image...or a nicer image ????
if yes, the you can upload any image you need and then use it here...
Tell me if you need more information...!!
Hope this helps.
Do reward each useful answer..!
Thanks,
Tatvagna.

Weblog: BSP extension for embedding word

Similar Messages

Maybe you are looking for