Documentation on Roll up in EC CS

Hi
I am looking for a good documentation on Roll ups on EC CS apart from what is available on online help. Appreciate if some one can help on this.
Regards

Hi,
For a start, you might want to try
http://help.sap.com/saphelp_47x200/helpdata/en/e9/cd0858635811d2995c0000e8a5999a/content.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/ECCS/ECCS.pdf
Hope this gives you a good headstart.
Cheers,
Gimmo

Similar Messages

Downgrading Oracle database ( Version 9.2.0.8.0 to 9.2.0.6.0)

Hi All,
I am working as development Dbs. I had upgraded Oracle DB 9.2.0.1.0 to version 9.2.0.8.0 for some testing purpose in Windows XP(32bit). I didnt take the backup before applying patch. Now they want to downgrade the db to 9.2.0.6.0. How can i do that? Is there any patch for that? or Is there any patch for downgrading to 9.2.0.1.0? Please let me know a solution.
Thanks,
Manikandan

I meant if the COMPATIBLE parameter has been set to something greater than 9.2.0.1 or 9.2.0.6 (depending on which you want to downgrade to). If it is still 9.2.0.0 that is fine.
Check the patch documentation for rolling back the 9.2.0.8 patch.

Setting up a rollout.

Is there a best practices guide to rolling out an iPad implementation? We are rolling out 30 ipads and I am sure it will snowball. Looking to head off any headaches by doing the set up right from the launch. We are a windows platform school.

We are doing an iPad pilot this year as well at my school. We purchased the Brettford cart, which holds 30 ipads and comes with charging stations for each of the ipads, and direct connectivity to the main computer managing the iPads, through one usb cable. We are obviously very early in our pilot, but have been very heppy with the cart as a part of the implementation. As far as managing the iPads, I would agree with gyrhead in that creating one school account for your apple purchases is a best practice. We created an acount [email protected] to cover all of our digital content, meaning that we can do our licenses for our desktops under that account as well. After hearing several horror stories of iTunes accounts/Apple accounts getting hacked, I would strongly recommend creating your account like we did. We created a new account, but used a gift card to create the account. This prevents a credit card from being associated with the account, so that if someone were to hack the school's apple account, they can only get as much as we have available on the gift card.
The next issue after the cart is rolled out is how to manage projects from a device meant for a single user, but shared amongst multiple students. We created a system for saving all fo the projects like this: "flastname##" (first initial last name) "Class Name" "Per. #" On the iPads, I used the iPhone configuration utility available for free download from apple right here: iphone config that link is for installing it on a windows machine. They have it available also for a mac machine. This will allow you to setup all of the wifi credentials in mass, setup whatever security settings you would like to have, restrictions and what we like, the mail setup.
After some testing, we are happy with how we setup email for the iPad cart. I created a generic email address for the cart: [email protected] and have it set to be a receive only account. How I did that was simply entering in an incorrect password for the incoming mail server. Then for the smtp server I put in the correct credentials. I could definitely get into more of the nitty gritty details on the rules I setup for my teacher accounts, so the emails are all automaticaly placed according to the class and period they are received, but do not want to be-labor this any more than is helpful. You can check out our blog documenting our roll-out if you would like: vcmsipad.blogspot.com

Track & Calculate Vehicle Milage

How do we track & Calculate Vehicle Milage in Oracle.Also looking for documentation on Rolling Assets.
Thanks!

Hi
Normally finance department handles this by using statistical accounts. You can have a vehicle expense account and link a statistical unit of measure 'Milage' to it. After you set a profile option enabling mixing of statistical and normal journals, when you enter a journal on the vehicle expense account, you can enter the milage data also.
Hope this helps.
Thanks

ORA-19046 with valid xsd-file (on 11.2.0.2)

Hello Experts,
I got an xml-file and had to import it into some relational tables. The xsd-files are given.
I tried: creating ressources for the xsd-files - works; register schema's -> not possible, because of ORA-19046.
In XMLSpy validating all xsd-files (a total of seven files) is possible - not error found.
Are there any ideas, how to import the data to some tables? (I don't really need the xml-file in the database)
Thanky for any help!
Frank

XSD-Upload - Part 1/7
There are seven files - I will post the ORIGINAL Files without oracle annotations:
vda_root_V1.2.xsd
-> vda_header_V1.2.xsd
-> vda_body_V1.2.xsd
-> ehd_root_V1.40.xsd
-> keytabs_V1.40.xsd
-> ehd_header_V1.40.xsd
-> datentypen_V1.40.xsd
My Probelm-baby ist datentypen_V1.40.xsd
<?xml version="1.0" encoding="ISO-8859-1"?>

<xs:schema xmlns="urn:ehd/001" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ehd/001" elementFormDefault="qualified" attributeFormDefault="unqualified">
     
     <xs:element name="id" type="id_typ">
          <xs:annotation>
               <xs:documentation>enthält eindeutige Instanz-ID</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="id_typ">
          <xs:attribute name="EX" type="xs:string" use="optional"/>
          <xs:attribute name="RT" type="xs:string" use="required"/>
          <xs:attribute name="RTV" type="xs:string" use="optional"/>
     </xs:complexType>
     <xs:complexType name="doc_id_typ">
          <xs:annotation>
               <xs:documentation>ist dem id_typ identisch</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="id_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="set_id" type="id_typ">
          <xs:annotation>
               <xs:documentation>enthält eindeutige Instanz-ID, die über alle Versionen und zusammgengehörende Dokumente konstant bleibt</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     
     <xs:element name="version_nbr" type="version_nbr_typ">
          <xs:annotation>
               <xs:documentation>Versionnummer des XML-Dokuments</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="version_nbr_typ">
          <xs:attribute name="V" type="xs:nonNegativeInteger" use="required"/>
     </xs:complexType>
     
     <xs:element name="document_relationship" type="document_relationship_typ">
          <xs:annotation>
               <xs:documentation>Beziehung zu anderen Dokumenten ("Anhang", "Ersatz")</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="document_relationship_typ">
          <xs:sequence>
               <xs:element name="document_relationship.type_cd" type="document_relationship.type_cd_typ">
                    <xs:annotation>
                         <xs:documentation>Art der Dokumentbeziehung ("Anhang", "Ersatz")</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element ref="related_document"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="document_relationship.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.101"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="related_document" type="related_document_typ">
          <xs:annotation>
               <xs:documentation>Verweis auf das Original/Anhang-Dokument</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="related_document_typ">
          <xs:sequence>
               <xs:element ref="id"/>
               <xs:element ref="set_id" minOccurs="0"/>
               <xs:element ref="version_nbr" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="document_type_cd" type="document_type_cd_typ">
          <xs:annotation>
               <xs:documentation>Dokumenttype Code</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="document_type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.100"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     
     <xs:element name="service_tmr" type="service_tmr_typ">
          <xs:annotation>
               <xs:documentation>Gültigkeitszeitraum (date..date)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="service_tmr_typ">
          <xs:complexContent>
               <xs:extension base="v_zeitraum_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="origination_dttm" type="origination_dttm_typ">
          <xs:annotation>
               <xs:documentation>Erstellungsdatum</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="origination_dttm_typ">
          <xs:complexContent>
               <xs:extension base="v_date_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     
     <xs:element name="intended_recipient" type="intended_recipient_typ">
          <xs:annotation>
               <xs:documentation>Empfänger / Zielgruppe der Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="intended_recipient_typ">
          <xs:sequence>
               <xs:element name="intended_recipient.type_cd" type="intended_recipient.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="intended_recipient.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.102"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="originator" type="originator_typ">
          <xs:annotation>
               <xs:documentation>Ersteller, Urheber des Dokuments / der Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="originator_typ">
          <xs:sequence>
               <xs:element name="originator.type_cd" type="originator.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="participation_tmr" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="originator.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.103"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="provider" type="provider_typ">
          <xs:annotation>
               <xs:documentation>Sender, Lieferant des Dokuments (kann gleichzeitig der Urheber sein)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="provider_typ">
          <xs:sequence>
               <xs:element name="provider.type_cd" type="provider.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="participation_tmr" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="provider.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.104"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="function_cd" type="function_cd_typ">
          <xs:annotation>
               <xs:documentation>Funktion/Rolle der Person/Organisation</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="function_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.105"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="participation_tmr" type="v_zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum/Zeitpunkt der Teilnahme</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     <xs:element name="person" type="person_typ">
          <xs:annotation>
               <xs:documentation>Person-Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:element name="group" type="group_typ">
          <xs:annotation>
               <xs:documentation>zugehörende Gruppe, Ausprägung (z.B. Augenarzt)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="group_typ">
          <xs:complexContent>
               <xs:extension base="v_s_string_typ">
                    <xs:sequence>
                         <xs:element ref="group.type_cd"/>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="group.type_cd" type="v_s_string_typ">
          <xs:annotation>
               <xs:documentation>Gruppebezeichnung (z.B. Facharztagruppe)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="person_typ">
          <xs:sequence>
               <xs:element ref="id" minOccurs="0"/>
               <xs:element ref="person_name" minOccurs="0"/>
               <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="telecom" type="v_string_typ">
          <xs:annotation>
               <xs:documentation>Telekomunnikation (tel,mail,fax,...)</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     <xs:element name="person_name" type="person_name_typ">
          <xs:annotation>
               <xs:documentation>Name der Person</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="person_name_typ">
          <xs:sequence>
               <xs:element name="nm" type="person_name_nm_typ"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="person_name_nm_typ">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="GIV" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Vorname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="MID" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Zusatzname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="FAM" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Nachname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="PFX" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Titel (Dr.)</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="SFX" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Namenzusatz</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="DEL" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Trennzeichen</xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:choice>
     </xs:complexType>
     
     <xs:element name="organization" type="organization_typ">
          <xs:annotation>
               <xs:documentation>Organisations-Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="organization_typ">
          <xs:sequence>
               <xs:element ref="id" minOccurs="0"/>
               <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="addr" type="addr_typ">
          <xs:annotation>
               <xs:documentation>Adresse</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="addr_typ">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="STR" type="v_string_typ"/>
               <xs:element name="HNR" type="v_string_typ"/>
               <xs:element name="POB" type="v_string_typ"/>
               <xs:element name="ZIP" type="v_string_typ"/>
               <xs:element name="CTY" type="v_string_typ"/>
               <xs:element name="STA" type="v_string_typ"/>
               <xs:element name="CNT" type="v_string_typ"/>
               <xs:element name="ADL" type="v_string_typ"/>
          </xs:choice>
     </xs:complexType>
     
     <xs:element name="patient" type="patient_typ">
          <xs:annotation>
               <xs:appinfo>Patient-Informationen</xs:appinfo>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="patient_typ">
          <xs:sequence>
               <xs:element name="patient.type_cd" type="v_s_string_typ" minOccurs="0"/>
               <xs:element ref="person"/>
               <xs:element name="birth_dttm" type="v_date_typ" minOccurs="0"/>
               <xs:element name="administrative_gender_cd" type="v_s_string_typ" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="local_header" type="local_header-cont.model">
          <xs:annotation>
               <xs:documentation>Element für weitere, datenartspezifische, Metainformationen</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="local_header-cont.model" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:any processContents="skip" minOccurs="0" maxOccurs="unbounded"/>
          </xs:choice>
          <xs:attribute name="ignore" type="ignore_typ" default="markup"/>
          <xs:attribute name="descriptor" type="xs:string"/>
          <xs:attribute name="render" type="xs:string"/>
     </xs:complexType>
     
     
     <xs:complexType name="v_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
     </xs:complexType>
     
     <xs:element name="TRANSLTN" type="transltn_typ">
          <xs:annotation>
               <xs:documentation>interne/alternative Kodes und Schlüsseltabellen</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="transltn_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <xs:complexType name="v_s_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="DN" type="xs:string" use="optional"/>
          <xs:attribute name="S" type="xs:string" use="optional"/>
          <xs:attribute name="SN" type="xs:string" use="optional"/>
          <xs:attribute name="SV" type="xs:string" use="optional"/>
     </xs:complexType>
     
     <xs:complexType name="v_date_typ">
          <xs:attribute name="V" type="xs:date" use="required"/>
     </xs:complexType>
     
     <xs:complexType name="v_zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum: datum..datum</xs:documentation>
          </xs:annotation>
          <xs:attribute name="V" type="zeitraum_typ" use="required"/>
     </xs:complexType>
     
     <xs:complexType name="pnxp_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="QUAL" type="xs:NMTOKENS" use="optional"/>
     </xs:complexType>
     
     
     
     
     
     <xs:element name="interface" type="interface_typ">
          <xs:annotation>
               <xs:documentation>enthält Informationen über die Schnittstelle selbst</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="interface_typ">
          <xs:sequence>
               <xs:element name="id" type="interface_id_typ"/>
               <xs:element name="interface.nm" type="interface_nm_typ"/>
               <xs:element name="version" type="interface_version_typ"/>
               <xs:element ref="originator" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element name="description" type="description_typ" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="interface_id_typ">
          <xs:complexContent>
               <xs:restriction base="id_typ">
                    <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.109"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="interface_nm_typ">
          <xs:annotation>
               <xs:documentation>Bezeichnung der Schnittstelle</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="v_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="interface_version_typ">
          <xs:annotation>
               <xs:documentation>Version der Schnittstellenbeschreibung</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="v_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="description_typ">
          <xs:annotation>
               <xs:documentation>Kurzbeschreibung oder Link auf die WebSite mit der Schnittstellenbeschreibung</xs:documentation>
          </xs:annotation>
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="URL" type="xs:anyURI" use="optional"/>
     </xs:complexType>
     
     <xs:element name="scope" type="scope_typ">
          <xs:annotation>
               <xs:documentation>Geltungsbereich</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="scope_typ">
          <xs:sequence>
               <xs:element name="id" type="scope_id_typ" maxOccurs="unbounded"/>
               <xs:element name="scope.type_cd" type="scope.type_cd_typ">
                    <xs:annotation>
                         <xs:documentation>z.B. 1=KV-Geltungsbereich</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="scope.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded">
                    <xs:annotation>
                         <xs:documentation>Name des Bereichs zu dem id-Element (z.B. KV-Nord)</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="scope_id_typ">
          <xs:complexContent>
               <xs:restriction base="id_typ">
                    <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.106"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:complexType name="scope.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.107"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="state" type="state_typ">
          <xs:annotation>
               <xs:documentation>Bearbeitungszustand</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="state_typ">
          <xs:complexContent>
               <xs:extension base="v_s_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     
     
     <xs:simpleType name="null.code.set">
          <xs:annotation>
               <xs:documentation>Ausprägungen für NULL-Attribut</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:enumeration value="NI"/>
               <xs:enumeration value="NA"/>
               <xs:enumeration value="UNK"/>
               <xs:enumeration value="NASK"/>
               <xs:enumeration value="ASKU"/>
               <xs:enumeration value="NAV"/>
               <xs:enumeration value="OTH"/>
               <xs:enumeration value="PINF"/>
               <xs:enumeration value="NINF"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="guid_typ">
          <xs:annotation>
               <xs:documentation>Typ für einen Global Unique Identifier</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:pattern value="[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum datum..datum</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:pattern value="([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|(\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.)"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ignore_typ">
          <xs:restriction base="xs:string">
               <xs:enumeration value="all"/>
               <xs:enumeration value="markup"/>
          </xs:restriction>
     </xs:simpleType>
</xs:schema>

Documentation for SolMan / ChaRM Security Rolls / Authorizations

Good Day;
I am currently setting up all the roles / authorizations for the different areas within Solution Manager / ChaRM.
I have been looking for a u201Cdetailedu201D document on all the security authorizations for Solution Manager / ChaRM. So far the only document I am able to find is the Security Guide for SAP Solution Manager 4.0 as of SP 15.
If there are more detailed documents, would someone point me in the right direction.
Regards
Don

Thanks Roel;
I am looking at user role authorizations.
The first thing I want to setup is the Team leader roles.
I need the team leader to have the ability to do the following
1.Create Issues
2.Create change requests
3.Change the status of a change request to u201CIn Developmentu201D
4.Create transports and tasks
5.Release transports
The Team leader will not have the authorization to u201Capprove u201C change requestsu201D
Thanks Again
Regards
Don

Mobile iPhone Application for SAP B1 Documentation

SAP releases the following statement on their landing page for their customers about using iPhone App in version 8.8. Direct copy and paste:
I am already using SAP Business One. Are there any requirements to be able to use this app?
You need to be running SAP Business One version 8.8 with a professional user license. Before you start using the app, make sure your SAP partner configures the mobility settings in SAP Business One.
Where is the documentation that is the checklist for installing and getting the mobile app up and running? You know, the usual documentation from step A to Z - go to Add-ons and do this, go to User and do this, etc. All I can find are videos/documents that are marketing oriented. I have the user guide "Setting Up Mobile Scenario in 8.8", but it is woefully lacking in several steps (ie, it says some fields are mandatory, but SAP does not even mention what "code" column is supposed to mean).
Anyone else have any luck digging out the pertinent information from SAP sites which SAP should have prominently highlighted to its partners before rolling this out? Where can I find it?
This all seems to be a rather disconnected roll-out.
Thanks in Advance - Zal

Here is part of the answer - Go here: https://websmp203.sap-ag.de/sbo-swcenter
Until it is changed, select "Updates" (not the other areas stated in some documentation, videos, and threads) and select "SAP Business 8.8", then "B1 8.8 Integration Component", and then it can be downloaded.
I will add more info as the process goes along, if there is anything more...
TIA - Zal

Roll method doesn't work properly

Hi there,
I ran into a problem with the roll method of GregorianCalendar class. Suppose the date is April 6, 00:00:00 2002, the following code will go throught the time changes:
GregorianCalendar cal = new GregorianCalender();
for (int i = 0; i < 24; i++) {
cal.roll(Calenader.HOUR_OF_DAY, 1);
April 6 01:00:00 2002
April 6 02:00:00 2002
April 6 22:00:00 2002
April 6 23:00:00 2002
April 6 00:00:00 2002
But if the current date is April 7, 2002 (daylight saving time change will occur at 2:00 am this day), the above code will result:
April 7 01:00:00 2002
April 7 02:00:00 2002
April 7 22:00:00 2002
April 7 23:00:00 2002
April 6 23:00:00 2002
April 6 00:00:00 2002
Can anyone tell me how to fix this problem or how to avoid this problem.
Thanks a lot.

It doesn't work quite that way for me, my first two lines are these:
April 6 01:00:00 PST 2002
April 6 03:00:00 PDT 2002
You'll notice that I printed the time zone out as well. My last three lines are these:
Sun Apr 07 23:00:00 PDT 2002
Sat Apr 06 23:00:00 PST 2002
Sat Apr 06 00:00:00 PST 2002
and I think there is an argument to be made that these are correct: applying roll() to Sun Apr 07 23:00:00 PDT 2002 should yield Sun Apr 07 00:00:00 PDT 2002; but since daylight saving time was not in effect at that moment, this is equivalent to Sat Apr 06 23:00:00 PST 2002, which is the actual result. On the other hand, here's a quote from the API documentation for Calendar:
"Roll rule. Larger fields are unchanged after the call."
which is an argument that they are incorrect: after the call, the hour should change but not the day. So I'd report it as a bug and see what answer you get.
How to fix the problem? What's the purpose of what you are doing?

Time Dimension Roll-Up Not Working

Hi Gurus,
We are on BPC NW 7.0 SP04. We are experiencing a strange problem with Time dimension. Even after defining the hierarchy correctly, the values are not being rolled up the hierarchy. Our requirement is to capture data at quarter level and year level. So we have defined the time dimension in following manner:
ID                     EVDESCRIPTION   PARENTH1     LEVEL         YEAR   PERIOD STYLE   MONTHNUM    TYPE   TIMEID           HLEVEL
2007.TOTAL     2007 TOTAL                               YEAR             2007     TOTAL   T3                12                       ACT   20070005        1
2007             2007                   2007.TOTAL   QUARTER     2007     Q1        T2                13                       ACT                        2
2007.Q1             2007 Q1                   2007.TOTAL   QUARTER     2007     Q1        T1                  3                       ACT   20070001        2
2007.Q2             2007 Q2                   2007.TOTAL   QUARTER     2007     Q2        T1                  6                       ACT   20070002        2
2007.Q3             2007 Q3                   2007.TOTAL   QUARTER     2007     Q3        T1                  9                       ACT   20070003        2
2007.Q4             2007 Q4                   2007.TOTAL   QUARTER     2007     Q4        T1                12                       ACT   20070004        2
Here TYPE is a custom dimension property . As the members depict, 2007.TOTAL value should be calculated as the sum of 2007.Q1, 2007.Q2, 2007.Q3 and 2007.Q4 (Quarters and Years are mutually exclusive in our case). But when we maintain data for Q1,Q2,Q3 and Q4, the TOTAL value is displayed as the value of Q4, and not the sum of quarters. We have tried changing MEASURES from PERIODIC to QTD and YTD, with no effect. We thought that it could be a problem with BI, and so built a simple BeX Query on top of the BPC application cube. But in the BEX query, the time dimension is properly aggregated, nd values are displayed correctly. So apparently it is not a problem with BI. In that case, we are missing something in BPC itself. Can any of you identify what it could be? Awaiting answers and Thanking in Advance.
Sincere Regards,
Amitabha

Amitabha,
It's just a problem that a lot of people run into when they are getting used to BPC. Once you see it happen to 10 or 15 people, you can start to recognize it pretty quickly
There are not a lot of examples of this in the Netweaver documentation. I think there are more in the Microsoft docs. However, there is mention of it on this page in the Netweaver documentation: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/65/84d6596224477d80cc8a4392e4c114/frameset.htm]
Ethan

Transaction roll back

          Dear Everyone,
          What kind of exceptions do the wls container force to roll back a transaction?
          Already a simple NullpointerException does it or it has to be a kind of special
          Exception like EJbException?
          And if I catch that exception I hope it does not roll the transaction back if
          I do not rethrow.
          Thanks for your help.
          Miklos


          Dear Deyan,
          Thanks for the answer. Actually an entity creation rolled back even I throw an
          CreateException.
          That is very intersting, and it is not mentioned in the sun documentation.
          Actually I catch the CreateException and rethrow it.
          Any idea why it happens?
          Miklos
          "Deyan D. Bektchiev" <[email protected]> wrote:
          >Miklos,
          >
          >Once the exception crosses the invocation wrapper if it is an instance
          >
          >of RuntimeException (NPE is) or RemoteException (this one is there
          >mostly for backward compatibility with pre-EJB 2.0 spec) the transaction
          >
          >will be marked for rollback so you cannot commit it.
          >If you don't want to roll back the transaction, throw an application
          >
          >exception instead (any other type that inherits from java.lang.Exception).
          >
          >Regards,
          >Dejan
          >
          >Miklos Molnar wrote:
          >
          >>Dear Everyone,
          >>
          >> What kind of exceptions do the wls container force to roll back a transaction?
          >> Already a simple NullpointerException does it or it has to be a kind
          >of special
          >>Exception like EJbException?
          >> And if I catch that exception I hope it does not roll the transaction
          >back if
          >>I do not rethrow.
          >>
          >> Thanks for your help.
          >>
          >> Miklos
          >>
          >>
          >

A Problem with Rolling forecast

Hi Experts,
Currently i have a problem in the Query Designer. Any help or suggestion will be very much appreciated.
The system that we have is BI 7.
What we want to have is a rolling forecast for the Profit and Loss Account.
It means that we will lock the previous periods against changes and open the coming periods for planning. In the query all 12 months have to be displayed.
For that purpose, I created 1 structure with 2 selections.
The 2 selections are
1. Closed Periods, which restricted to 0fiscper 001.2007-003.2007
2. Open periods, which restricted to 0fiscper 004.2007-012.2007.
Then I drill it down with 0fiscper so that I can see 12 months.
The problem is now that when I do not surpress the zeros, then I will see 2 times 12 months instead of only 12 months.
But on the other hand, I cannot surpress zero since I also want to see and be able to do planning on the zero values accounts (for example on the open periods).
Does anyone know how to solve this problem, so that I only see 12 months in my query, but also be able to see zero values on the open periods?
Otherwise, does anyone have any other solution to solve the rolling forecast? (any links or documentation?)
Thank you very much in advance.
Best regards,
Fen

Hi Venkat,
In the new BI Integrated, we can close and open the periods by put the indicator for close and open periods on the query designer.
The report that I am aiming for will look like this:
Closed Periods                               Open Periods
January         February      March     April       May      June    July ...... December
For that I created 1 Structure with 2 Selections.
The selections is restricted as follows:
Closed Periods --> 0fiscper 001.2007-003.2007
Open Periods ---> 0fiscper 004.2007-012.2007
and then I drill it down with 0fiscper.
But instead of giving me the periods that I restricted it gave me the following:
Closed Periods                    Open Periods
January   February March    January    February    March
Best regards,
Fen

Rolling Cluster Upgrade (OES2 to OES11) - GPT partition

We've got an OES2 SP3 cluster that we'll be rolling cluster upgrading to OES11 SP2.
We are currently at max capacity for several of the NSS volumes (2 TB).
If I'm reading/interpreting the OES11 SP2 docs correctly:
AFTER the cluster upgrade is complete, the only way I can get to larger volumes will be to create new LUNs on the SAN and intialize those with GPT. Then I could do the NSS Pool Move feature to get the existing 2 TB volumes to the larger setup?
Is that correct?
Or is there a better way that doesnt' require massive downtime?

Originally Posted by konecnya
In article <[email protected]>, Kjhurni wrote:
> We are currently at max capacity for several of the NSS volumes (2 TB).
I was on the understanding that you could bind multiple partitions to
create NSS volumes up to 8TB. But I'd be hesitant to do that for a
clustered volume as well.
> I could do the NSS Pool Move feature to get the existing 2 TB
> volumes to the larger setup?
> Or is there a better way that doesnt' require massive downtime?
My first thought is the migration wizard so that the bulk of the copy can
be done while system is live but in the quieter times. Then the final
update with down time should be much faster.
But then do you really need down time for the Pool Move feature?
https://www.novell.com/documentation...a/bwtebhm.html
Certainly indicates it can be done live on a cluster with the move
process being cluster aware.
Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
Migration = pew pew (re-doing IP's/etc and copying 4 TB of data is ugly especially when it's lots of tiny stuff).
haha
Anyway, when I asked about a better way that doesn't require massive downtime what I meant was:
Is there a better way vs. Pool Move that doesn't require massive downtime (in other words, the "other way" having the massive downtime, not the Pool Move).
Choice A = Pool Move = No downtime
But let's say that's not a good option (for whatever reason) and someone says use Choice B. But Choice B ends up requiring downtime (like the data copy option).
I just didn't know if Pool Move required that you create the partition ahead of time (so you can choose GPT) or if it kinda did it all for you on the fly (I'll have to read up when I get to that point).
I'm not terribly keep on having multiple DOS partitions, although that technically would work. Just always scares me. It's just temporary for the next 8 months anyway while we migrate to NAS from OES, but I'm running out of space and am on an unsupported OS anyway.

Roll out requirements of SAP in European countries

Dear All,
We are in the process of rolling out SAP to our client's European business units based on our US based global template. Is there any documented procedural steps one must follow so that we do not miss any of the statutory/Legal requirements and some country specific functionality (config, reports etc) ?
We are presently looking for the countries Po, Hu, Be, Ru, Sp, It & UK. We are currently looking at country specific best practices baseline packages in Sap services Marketplace but if anyone can provide an exhaustive list of activities based on their past implementations, it'll be very much helpful.
Warm regards,
Kingsuk Mukherjee

a common requirement in all countries of the European union is Intrastat trade reporting.
And even it is common in EU countries, it can slightly vary from country to country, and Italy the most complicated in this regard.
For Russia you should implement the country version
for Belgium there is special OSS note "how to setup Belgium company code"
(and an umbrella is needed in Belgium, not a legal requirement, but a personal. I never had a worse whether anywhere else than the year I worked in Belgium)
You should do you fit/gap analysis on site to see whats missing.
It is always surprising especially if you have 2 companies in one country, they have different "legal" requirments. Just had it today. we are merging SAP systems, and both systems have a company in Italy.

Roll up to initiatives not (completely) working

Hi everyone,
The context
We're running a PS module on one system and a PPM module (CPRXRPM 500_702) on another.
In PS, we have a bunch of PS Projects with lots of WBS, Networks and Activities, on which there are costs.
In PPM, we have one Item per PS Project (they're properly linked in rpm_obj_link), and these Items are related to some Initiatives and some Buckets, everything being related to a single Portfolio.
What we're trying to do
We're using /RPM/FICO_INT_PLANNING to roll up costs from the PS Projects into the PPM Items, Buckets and Initiatives. We're using option "Integr., Planning and Rollup" of that program.
All the configuration to enable this has been done and double-checked, as per the official documentation.
The issue
While roll up on Buckets and Items are OK, roll up on Initiatives is not. When looking into NWBC's financial views, we have zeroes everywhere, instead of the sum of the related items.
We noticed that the corresponding entry in financial view table V_INM_INIT_DB is missing, despite the data in the related tables being complete. It's as if we just need that one entry to be created for the NWBC to work.
The only way we managed to make it work is by changing the financial period breakdown on the Initiative (from annual to something else, then back to annual). Then if we run the roll up again it works. However, we have a lot of Initiatives to handle and will have more in the future, so a manual fix is not a good enough solution. Besides, this works only when done via NWBC (see below).
What we already tried to solve it
- we triple-checked the configuration of both systems, everything is fine
- we installed notes 2023535, 1996720, 2007537, 2057988 and 1909853 in hopes it would fix the roll up program, it didn't help our issue
- we used /RPM/PLAN_INT_PREP on both Items and Initiatives in hopes it would generate the Initiatives' views, it made no difference
- we tried defining the period breakdown on both the Item and the Initiative upon their creation (instead of letting the system set the default)
- we reproduced the period breakdown trick in code by using INM_INITIATIVE_MODIFY, but it does not "unblock" the Initiative like it does in NWBC
- we tried to find where and when the financial view is created, but V_INM_INIT_DB is not used anywhere in the system apparently!?
- searching online for infos on both V_INM_INIT_DB and /RPM/FICO_INT_PLANNING did not bring much information
My questions to you
- anybody met a similar issue previously? How did you solve it?
- any ideas on where to look or what to try next? We're kind of out of ideas here, and running short on time, as we'll start the user testing soon.
I'm currently trying to trace and debug what's happening in both the roll up program and NWBC, to see if I can understand what's wrong. But this is a lengthy process, especially considering I don't even know what to look for. So any help and ideas would be greatly appreciated!
Kind regards,
Jonathan

Hi Chatsworth,
Here are our financial categories:
...and their groups:
The financial views:
...and their front-end display:
And finally mapping the views to the cost elements:
Thank you for your time!
Kr,
Jonathan

Regarding copy of documentation of previous project in sap sd

hi,
In copy of documentation of previous project we need to copy the same to fill up gaps from sd,mm and even pp side for which it will be used for future roll outs/impementations of the projects.as iam new to documentation, i need guidance for copying the documentation.can anybody please helpme.

hi sridhar,
i mean to say the previous project documentation will be copied by filling up gaps to provide the same for future roll outs/implementations which will be uploaded in r/3.thank you for your reply.

Documentation on Roll up in EC CS

Similar Messages

Maybe you are looking for